From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Unable to mount snapshot LV when fs=ext3 on Linux kernel 2.4.20
Date: Thu Apr 17 07:53:02 2003 [thread overview]
Message-ID: <20030417125259.GF1082@tykepenguin.com> (raw)
In-Reply-To: <3E9EA132.3020902@bull.net>
On Thu, Apr 17, 2003 at 02:42:26PM +0200, Michel Seyller wrote:
> Hi,
>
> Linux Red Hat 9.0 kernel 2.4.20-8
> I have created a ext3 fs on a LVM logical volume : OK.
> create a snapshot on it, trying to mount it :
>
> [root@linux05 proc]# mount /dev/volume01/snap01 /SNAP
> mount: block device /dev/volume01/snap01 is write-protected, mounting
> read-only
> mount: wrong fs type, bad option, bad superblock on /dev/volume01/snap01,
> or too many mounted file systems
>
>
> No problem with an ext2 file system.
>
> Any explanation ? a bug ? a bad patch for VFS locking in the kernel ?
Sounds like the VFS lock patch is not in the RH kernel, or is not patched in
correctly.
--
patrick
prev parent reply other threads:[~2003-04-17 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 7:42 [linux-lvm] Unable to mount snapshot LV when fs=ext3 on Linux kernel 2.4.20 Michel Seyller
2003-04-17 7:53 ` Patrick Caulfield [this message]
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=20030417125259.GF1082@tykepenguin.com \
--to=caulfield@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox