Date: Wed, 9 Jun 2004 00:35:28 +0200
From: Matthias Andree <matthias.andree@gmx.de>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.26 JFS: cannot mount
Message-ID: <20040608223528.GA13241@merlin.emma.line.org>
Mail-Followup-To: Dave Kleikamp <shaggy@austin.ibm.com>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
References: <20040608195610.GA4757@merlin.emma.line.org> <20040608201446.GA13764@merlin.emma.line.org> <1086727014.26567.20.camel@shaggy.austin.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1086727014.26567.20.camel@shaggy.austin.ibm.com>
User-Agent: Mutt/1.5.5.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 943
Lines: 23

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), ext3 and reiserfs can replay the log
in kernel or user space whichever touches first...

-- 
Matthias Andree

Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
-
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/