https://qa.mandrakesoft.com/show_bug.cgi?id=1320
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
Version|2.4.21-0.pre4.3mdk |2.4.21-0.pre4.5mdk
------- Additional Comments From [EMAIL PROTECTED] 2003-02-11 06:12 -------
As of the latest kernel:
Linux version 2.4.21pre4-5mdk ([EMAIL PROTECTED]) (gcc version 3.2.1
(Mandrake Linux 9.1 3.2.1-6mdk)) #1 Sat Feb 8 23:06:55 CET 2003
I see in the changelog that the LVM vfslock patch is supposed to be in the
kernel now, which in and of itself is good. However it does not seem to be
doing what it is supposed to (appologies for line wrapping -- 'tis bugzilla's
fault):
# lvcreate -s -L 100M -n root_snap /dev/rootvol/root
lvcreate -- WARNING: the snapshot will be automatically disabled once it gets full
lvcreate -- INFO: using default snapshot chunk size of 64 KB for
"/dev/rootvol/root_snap"
lvcreate -- doing automatic backup of "rootvol"
lvcreate -- logical volume "/dev/rootvol/root_snap" successfully created
# mount /dev/rootvol/root_snap /mnt/root_snap/
mount: block device /dev/rootvol/root_snap is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/rootvol/root_snap,
or too many mounted file systems
# dmesg
Linux version 2.4.21pre4-5mdk ([EMAIL PROTECTED]) (gcc version 3.2.1
(Mandrake Linux 9.1 3.2.1-6mdk)) #1 Sat Feb 8 23:06:55 CET 2003
...
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access unavailable, cannot proceed.
which is what happens when the vfslock patch is not applied/working.
b.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: __UNKNOWN__
status: REOPENED
creation_date:
description:
The kernel desperately needs the vfslock patch from the LVM project in order to
support snaphots of journalled filesystems. Since Mandrake Linux supports LVM
and it also supports journalling filesystems, it not supporting LVM snapshots of
journalling filesystems is simply a bug.
