From: Chris Mason <mason@suse.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] mounting ext3 snapshot occasionaly fails
Date: Tue Dec 3 10:18:02 2002 [thread overview]
Message-ID: <1038932284.1381.0.camel@tiny> (raw)
In-Reply-To: <20021203124412.GJ2227@tykepenguin.com>
On Tue, 2002-12-03 at 07:44, Patrick Caulfield wrote:
> On Tue, Dec 03, 2002 at 12:35:09PM +0000, Tomaz Beltram wrote:
> > Hi,
> >
> > I have similar problems as described in this mailing list some months ago,
> > regarding mounting snapshots of journaled file systems.
> >
> > Mounting the snapshot fails and dmesg shows:
> > EXT3-fs: INFO: recovery required on readonly filesystem.
> > EXT3-fs: write access unavailable, cannot proceed.
> >
> > I have observed that the failure is more frequent with longer delays
> > between snapshot creation and mount time.
> >
> > The problem was solved with the VFS-lock patch for 2.4.18 kernel. But I am
> > using LVM 1.0.5 and 2.4.19-SuSE kernel (64GB-SMP). As I understand, it
> > should already have the VFS-lock patch applied. If not, where can I find
> > one?
>
> I don't know whether the SuSE kernel has the VFS lock patch applied or not - if
> not then one for 2.4.19 is available in the LVM 1.0.6 source package.
>
> The patch is agains the Linus kernel so whether it will apply to the SuSE
> kernel is something you'll have to find out for yourself I'm afraid !
The suse kernel already has the patch, so there might be a timing
problem in the ext3 support.
-chris
next prev parent reply other threads:[~2002-12-03 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 6:35 [linux-lvm] mounting ext3 snapshot occasionaly fails Tomaz Beltram
2002-12-03 6:44 ` Patrick Caulfield
2002-12-03 10:18 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 10:24 Tomaz Beltram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1038932284.1381.0.camel@tiny \
--to=mason@suse.com \
--cc=linux-lvm@sistina.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.