2.4.17rc2

Did a bunch of stuff get updated in the 2.4.17rc2 kernel? I ask because I just applied that patch to 2.4.16, and at one point patch stated it looked like a patch had already been applied.

Share and Enjoy. 

Sure, 2.4.17 contains a lot of little fixes over 2.4.16. I think it may be
safe to skip that part. Anyway, what file is reported to be already applied? Cheers, GCS

Hi..

I've been using LVM for an year now... and have had almost no problems with it...

Lately, i decided to start using snapshots to backup some data. I created snapshot volumes as per the lvcreate man page and the LVM-HOWTO on the sistina web site... however, i get stuck everytime i try to moung the snapshot...

mount gives the following error:

-------

anubhav:~# mount /dev/data/snap_work /mnt
mount: block device /dev/data/snap_work is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/data/snap_work,
       or too many mounted file systems
-------

lvdisplay output is as follows:

-------

anubhav:~# lvdisplay /dev/data/snap_work
--- Logical volume ---
LV Name                /dev/data/snap_work
VG Name                data
LV Write Access        read only
LV snapshot status     active destination for /dev/data/work
LV Status              available
LV #                   5
# open                 0
LV Size                2.50 GB
Current LE             640
Allocated LE           640
snapshot chunk size    64.00 KB
Allocated to snapshot  0.00% [0/590.62 MB]
Allocated to COW-table 9.38 MB
Allocation             next free
Read ahead sectors     10000
Block device           58:8
-------

I'm attaching the output of vgdisplay -v /dev/data in a gzipped file... so as not to clutter this email...

I am using kernel version 2.4.17 with LVM version 1.0.2. I've applied all the kernel patches correctly. And i'm using ReiserFS as the filesystem. The mount version that i am using is: mount-2.11n

can anyone guide me as to where i am going wrong...??

thanks,

abhas.

-------------------------------------------------------------------
Abhas Abhinav		   | Free Software at its product-ive best.
CEO, DeepRoot Linux
http://www.deeproot.co.in	   	   ---- Server Appliances ----
Ph: +91 (80) 856 5624	       ---- Linux Support and Services ----
-------------------------------------------------------------------

You need the "VFS-lock" patch, from the LVM CVS repository.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

I'm under 2.4.17, which patch do I have to get to use snapshot ? The linux-2.4.11-VFS-lock.patch or linux-2.4.18-VFS-lock.patch ?

Can I use whatever file system I want for snapshots ?

Thanks

Pierrick

Use the 2.4.11 patch for kernel 2.4.17

Without the patch only (I think) ext2 will work with snapshots, the journalling filesystems need the VFS patch.

patrick

Probably 2.4.11 is the right one.

Journaling filesystems need a special interface, but reiserfs, ext3, and XFS all support this interface. For non-journaled filesystems, it will just sync the device, but this is not 100% guaranteed to make the fs consistent. Also, when you mount an ext2 filesystem it will report the filesystem as dirty, but it will still mount, unlike ext3.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

Yes, you probably mean the patch from patch-2.4.17

    --- linux-2.4.16/drivers/md/lvm-snap.c  Mon Nov 12 17:34:20 2001
    +++ linux/drivers/md/lvm-snap.c Fri Dec 21 16:40:32 2001
    @@ -542,8 +542,6 @@
     
     void lvm_snapshot_release(lv_t * lv)
     {
    -       int     nbhs = KIO_MAX_SECTORS;
    -
    	    if (lv->lv_block_exception)
    	    {
    		    vfree(lv->lv_block_exception);

which seems already to be in LVM-1.0.1. This patch in uncritical anyway since it does nothing, except cosmetic cleanup (removal of unused variable).

urs