Date: Wed, 9 Jun 2004 10:12:44 +1000
From: Nathan Scott <nathans@sgi.com>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.26 JFS: cannot mount
Message-ID: <20040609101244.G1200131@wobbly.melbourne.sgi.com>
References: <20040608195610.GA4757@merlin.emma.line.org> <20040608201446.GA13764@merlin.emma.line.org> <1086727014.26567.20.camel@shaggy.austin.ibm.com> <20040608223528.GA13241@merlin.emma.line.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20040608223528.GA13241@merlin.emma.line.org>; from matthias.andree@gmx.de on Wed, Jun 09, 2004 at 12:35:28AM +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1104
Lines: 28

On Wed, Jun 09, 2004 at 12:35:28AM +0200, Matthias Andree wrote:
> On Tue, 08 Jun 2004, Dave Kleikamp wrote:
> 
> > No, all of the code to replay the journal is in user space.  JFS does
> > allow a read-only mount when the superblock is dirty.  This allows
> > fsck.jfs to replay the journal while the root is mounted read-only.  /
> > can then be remounted rw after fsck runs.
> 
> So was the mount was refused because a) the read-only
> option was missing while b) the file system needed a journal replay?
> 
> Interesting difference. XFS insists on replaying the log in kernel space
> (user space can only zero the log),

FWIW, all of the log replay code is there in userspace, so it
should just be a "simple matter of programming" to implement
this for XFS (noone has ever done so though, and its never
really been a priority for us).

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/