lvm snapshot fails
I'm attempting to create a snapshot volume for a 50GB partition, however the lvcreate fails with the following error:
$ lvcreate -L1G -s -n wwwsnap /dev/vg00/www lvcreate -- WARNING: the snapshot will be automatically disabled once it gets full lvcreate -- INFO: using default snapshot chunk size of 64.00 KB for "/dev/vg00/wwwsnap" File size limit exceeded
strace shows it's getting a EFBIG error -
open("/dev/sdc1", O_WRONLY) = 4_llseek(4, 214756169728, [214756169728], SEEK_SET) = 0write(4, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 512) = -1 EFBIG (File too large) --- SIGXFSZ (File size limit exceeded) ---
+++ killed by SIGXFSZ +++
This is with 2.4.17, patched with 1.0.1 and 1.0.1 userland tools.
Here's my pvscan:
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- ACTIVE PV "/dev/sdc1" of VG "vg00" [457.98 GB / 257.98 GB free]
pvscan -- total: 1 [457.99 GB] / in use: 1 [457.99 GB] / in no VG: 0 [0]
Is there a special 64bit flag I need to set somewhere to allow the lvmtools to deal with a device that large?
-D
--
When Hell freezes over, I'll snowboard there too.
Quoted 9 lines · Daniel Sully
I'm attempting to create a snapshot volume for a 50GB partition, however the lvcreate fails with the following error:
$ lvcreate -L1G -s -n wwwsnap /dev/vg00/www lvcreate -- WARNING: the snapshot will be automatically disabled once it gets full lvcreate -- INFO: using default snapshot chunk size of 64.00 KB for "/dev/vg00/wwwsnap" File size limit exceededstrace shows it's getting a EFBIG error -
This is a kernel problem, added since 2.4.10, and fixed in 2.4.18-pre1. You need to log into this system directly as root (no "su" or "sudo") because it seems you are trying to set a ulimit somewhere, and the kernel also prevents you from setting a real ulimit with glibc-2.1.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
Once upon a time Andreas Dilger shaped the electrons to say...
Quoted 4 lines
This is a kernel problem, added since 2.4.10, and fixed in 2.4.18-pre1. You need to log into this system directly as root (no "su" or "sudo") because it seems you are trying to set a ulimit somewhere, and the kernel also prevents you from setting a real ulimit with glibc-2.1.
Thanks. That fixed the problem.
-D
--
Cracking toast Gromit!