Date: Wed, 6 Aug 2003 11:52:14 -0700
From: Mike Fedyk <mfedyk@matchmail.com>
To: Jan Niehusmann <jan@gondor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uncorrectable ext2 errors
Message-ID: <20030806185214.GD21290@matchmail.com>
Mail-Followup-To: Jan Niehusmann <jan@gondor.com>,
	linux-kernel@vger.kernel.org
References: <20030806150335.GA5430@gondor.com> <20030806110634.G7752@schatzie.adilger.int> <20030806183822.GA6744@gondor.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030806183822.GA6744@gondor.com>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 772
Lines: 15

On Wed, Aug 06, 2003 at 08:38:22PM +0200, Jan Niehusmann wrote:
> Can you explain how a r/o mounted file system can cause problems?
> Perhaps there is still some connection to my problem.

No it shouldn't cause problems, only that you should umount the filesystem
before you mount it read/write because the fsck might have changed
something, and the kernel will have the old information still in memory, and
might cause MORE corruption, than before.

So, just umount after fsck and you should be set (at least for that part)...
-
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/