From: Wolfgang Weisselberg <weissel@netcologne.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] mount reiserfs snapshot failed
Date: Thu Apr 18 08:07:01 2002 [thread overview]
Message-ID: <20020418130718.GA30701@tiger.bigcats.invalid> (raw)
In-Reply-To: <20020418094402.GA1233@fib011235813.fsnet.co.uk>
Hi, Joe!
Joe Thornber (joe@fib011235813.fsnet.co.uk) wrote 31 lines:
> On Thu, Apr 18, 2002 at 11:33:31AM +0200, Markus Bartl wrote:
> > Im using the original kernel 2.4.18 with the locking patch and the
> > lvm-patch applied. I use the lvm in Version 1.1rc1.
> > In some cases mounting the snapshot volume fails with error 32 (wrong fs
> > type or bad superblock).
> Do version 1.0.3 tools fail in the same way ?
I am running a similar configuration:
Kernel 2.4.18-rc4
+ LVM 1.0.3
+ linux-2.4.18-VFS-lock.patch
+ sched-O1-2.4.18-pre8-K3.patch
I use ext3, and the LVM 1.0.3-tools + LVM-1.0.3-pmove-patch
Snapshots work.
I upgrade to 2.4.19-pre6, must merge the VFS-lock.patch by hand
and drop the sched-O1-* patch; and use the LVM 1.1rc1-Tools:
Snapshots get generated, but first some (depending on the
order of generation!), later all of them are unreadable (even
a simple cat fails complaining about that), so mount fails.
I decide this might be due to a bad merge on my side or a
kernel problem, so I downgrade to:
Kernel 2.4.18-rc4
+ LVM 1.1rc1
+ linux-2.4.18-VFS-lock.patch
+ sched-O1-2.4.18-pre8-K3.patch
LVM 1.1rc1-Tools.
Snapshots still unreadable.
I downgrade the Kernel to LVM 1.0.3:
Kernel 2.4.18-rc4
+ LVM 1.0.3
+ linux-2.4.18-VFS-lock.patch
+ sched-O1-2.4.18-pre8-K3.patch
but still with LVM 1.1rc1-Tool
Snapshots still show the same problems as before.
Downgrading to LVM 1.0.3-tools on the running system:
everything works again.
-Wolfgang
next prev parent reply other threads:[~2002-04-18 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 4:36 [linux-lvm] mount reiserfs snapshot failed Markus Bartl
2002-04-18 4:43 ` Joe Thornber
2002-04-18 5:56 ` Markus Bartl
2002-04-18 7:14 ` Xavier Montagutelli
2002-04-18 6:39 ` Markus Bartl
2002-04-18 7:05 ` Chris Mason
2002-04-18 8:07 ` Wolfgang Weisselberg [this message]
2002-04-19 8:13 ` Heinz J . Mauelshagen
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=20020418130718.GA30701@tiger.bigcats.invalid \
--to=weissel@netcologne.de \
--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.