From: Chris Mason <mason@suse.com>
To: Andreas Dilger <adilger@turbolinux.com>, linux-lvm@sistina.com
Cc: reiserfs-list@namesys.com
Subject: Re: [reiserfs-list] Re: [linux-lvm] mounting reiserfs snapshot fails
Date: Fri, 13 Apr 2001 19:53:58 -0500 [thread overview]
Message-ID: <398930000.987209638@tiny> (raw)
In-Reply-To: <200104140023.f3E0NSIm014650@webber.adilger.int>
On Friday, April 13, 2001 06:23:28 PM -0600 Andreas Dilger
<adilger@turbolinux.com> wrote:
> Ed Tomlinson writes:
>> Using debian sid, 2.4.3-ac5, lvm 0.91 beta7, with the vfs locking
>> patch applied I get:
>>
>> oscar# mount /dev/lv/snap /snap -t reiserfs -oro
>> mount: wrong fs type, bad option, bad superblock on /dev/lv/snap,
>> or too many mounted file systems
>>
>> When trying to mount the snap shot. It was created with:
>> lvcreate -L 1G -s -n snap /dev/lv/root /dev/hdg1
>> without problems
>
> Are you sure that the VFS patch is applied, and that the LVM and
> reiserfs code was compiled with "enable VFS patch" (whatever it is
> called) enabled? That has been a source of problems in the past.
> The patch was applied, but you also need to enable it for both the
> reiserfs and LVM code.
That would be a different error, reiserfs would complain that it found a
filesystem, but was unable to mount it because it needed replay and the
device was readonly. In this case, the snapshot is not a valid FS at all,
even though the source looks fine.
I'll upgrade to the latest LVM and try to reproduce...
-chris
next prev parent reply other threads:[~2001-04-14 0:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 17:29 [linux-lvm] mounting reiserfs snapshot fails Ed Tomlinson
2001-04-13 20:36 ` Chris Mason
2001-04-13 22:42 ` Ed Tomlinson
2001-04-14 0:23 ` Andreas Dilger
2001-04-14 0:53 ` Chris Mason [this message]
2001-04-18 1:38 ` [reiserfs-list] " Ed Tomlinson
2001-04-30 1:48 ` [linux-lvm] Re: [reiserfs-list] " Chris Mason
2001-04-30 4:23 ` Ed Tomlinson
2001-04-30 4:31 ` Ed Tomlinson
2001-04-30 11:43 ` Chris Mason
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=398930000.987209638@tiny \
--to=mason@suse.com \
--cc=adilger@turbolinux.com \
--cc=linux-lvm@sistina.com \
--cc=reiserfs-list@namesys.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.