RE: [Evms-devel] newbie question - cannot mount snapshot volume

[Chia C. <chi...@zy...>]

Hi Kevin,

Thanks very much for the pointers. Indeed I did not follow section 2.B.5 ---
I was using device-mapper-1.00.05 instead of device-mapper-1.00.02
referenced in the INSTALL file, so I mistakenly assumed that the extra
package 2.4.21-dm-3.tar.bz2 is not needed.

So I went to http://people.sistina.com/~thornber/patches/2.4-stable/2.4.21
directory and noticed that there is a newer version 2.4.21-dm-4.tar.bz2 so I
downloaded that version. This version has 4 more patches but I ignored them
since they are not mentioned in the INSTALL file (00012 - 00015).

However, when I tried to follow the INSTALL file to apply the reelvant
patches, most of them encountered problems:

00002, 00003, 00004, 00009, 00010:
Reversed (or previously applied) patch detected! [I chose default to ignore
them]

00011:
patching file driver/md/Config.in
Hunk #1 failed at 14

00005:
patching file driver/md/dm-snapshot.c
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file
drivers/md/dm-snapshot.c.rej
patching file driver/md/lvm.c
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file drivers/md/lvm.c.rej
patching file fs/buffer.c
Hunk #1 succeeded at 395 with fuzz 1 (offset 32 lines).
patching file fs/reiserfs/super.c
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file fs/reiserfs/super.c.rej
patching file fs/super.c
Hunk #1 succeeded at 45 with fuzz 1 (offset 7 lines)
Hunk #2 succeeded at 499 with fuzz 1 (offset 20 lines)
Hunk #3 succeeded at 545 with fuzz 1 (offset 40 lines)
patching file include/linux/fs.h
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file include/linux/fs.h.rej
patching file kernel/ksyms.c
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
1 out of 1 hunk ignored -- saving frejects to file kernel/ksyms.c.rej

00006:
patching file drivers/md/dm-snapshot.c
Reversed (or previously applied) patch detcted! Assume -R? [n][hit return]
Apply anyway? [n] [hit return]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file
drivers/md/dm-snapshot.c.rej

00007:
patching file drivers/md/dm-snapshot.c
Hunk #1 succeeded at 580 (offset 56 lines).
patching file drivers/md/dm.c

I wonder maybe these patching problems are related to the fact that I used a
different base device-mapper package? Should I also apply any of the newer
patches (00012 - 00015)?

Thanks

Chia


-----Original Message-----
From: Kevin Corry [mailto:kev...@us...]
Sent: Tuesday, September 23, 2003 7:45 AM
To: Chia Chao; evm...@li...
Subject: Re: [Evms-devel] newbie question - cannot mount snapshot volume


Hi Chia,

On Monday 22 September 2003 19:44, Chia Chao wrote:
> Hi
>
> I created a snapshot volume but attempts to mount this volume resulted in
> error:
>
> Engine: mount: mount: block device /dev/evms/sv is write-protected,
> mounting red-only

This just means you created the snapshot as read-only instead of writeable.

> mount: wrong fs type, bad option, bad superblock on /dev/evms/sv, or too
> many mounted file systems

Generally you'll see this error when you're taking a snapshot of a journaled
filesystem and you haven't applied the VFS-lock patch to the kernel. Did you
read through the INSTALL file in the 2.1.1 package when installing EVMS? Did
you follow section 2.B.5?

Also, is this an ext2 or an ext3 filesystem? It will make a difference in
this
case.

> EXT2-fs: device-mapper(254,16)couldn't mount because of unsupported
> optional features (4).

I don't think I've ever seen this error before. I'll have to search through
the kernel source to see what triggers it.

> This is a 2.4.21 kernel with device-mapper-1.00.05 and evms-2.1.1. The
> original volume is an evms volume (EXT2/3), and the snapshot volume is
also
> an evms volume created from a snapshot object (no FS).
>
> Thanks
>
> Chia

--
Kevin Corry
kev...@us...
http://evms.sourceforge.net/