From wil_c_will at hotmail.com Sat Aug 4 13:26:38 2012 From: wil_c_will at hotmail.com (william L'Heureux) Date: Sat, 4 Aug 2012 09:26:38 -0400 Subject: resize too large Message-ID: I have a file system I am trying to resize via resize2fs but I get this error resize2fs 1.41.14 (22-Dec-2010) resize2fs: New size too large to be expressed in 32 bits im on debian squeeze 2.6.32-5-amd64 # pvs ? PV???????? VG????? Fmt? Attr PSize? PFree ? /dev/md1?? vgRAID6 lvm2 a-?? 18.17t 134.12g # lvs ? LV??? VG????? Attr?? LSize? Origin Snap%? Move Log Copy%? Convert ? data1 vgRAID6 -wi-ao 18.00t and the cryptsetup resize worked like a charm. I ran? e2fsck before the resize which pass sucessfully. I added ext4 = { ??????????????? features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize ??????????????? auto_64-bit_support = 1 ## ADDED THIS ??????????????? inode_size = 256 ??????? } to /etc/mke2fs.conf and run resize2fs and got the same error From pg_ext3 at ext3.for.sabi.co.UK Sun Aug 5 12:56:58 2012 From: pg_ext3 at ext3.for.sabi.co.UK (Peter Grandi) Date: Sun, 5 Aug 2012 13:56:58 +0100 Subject: resize too large In-Reply-To: References: Message-ID: <20510.28083.108602.614603@tree.ty.sabi.co.UK> > [ ... ] im on debian squeeze 2.6.32-5-amd64 [ ... ] > resize2fs: New size too large to be expressed in 32 bits [ ... ] > ? data1 vgRAID6 -wi-ao 18.00t Thanks for letting us know that 'resize2fs' and 'ext3' and the Linux kernel continue to behave as documented. [ ... ] From pg_ext3 at ext3.for.sabi.co.UK Mon Aug 6 22:49:23 2012 From: pg_ext3 at ext3.for.sabi.co.UK (Peter Grandi) Date: Mon, 6 Aug 2012 23:49:23 +0100 Subject: resize too large In-Reply-To: References: <20510.28083.108602.614603@tree.ty.sabi.co.UK> Message-ID: <20512.18956.737375.920361@tree.ty.sabi.co.UK> >> [ ... ] im on debian squeeze 2.6.32-5-amd64 [ ... ] >> resize2fs: New size too large to be expressed in 32 bits [ >> ... ] data1 vgRAID6 -wi-ao 18.00t >> Thanks for letting us know that 'resize2fs' and 'ext3' and >> the Linux kernel continue to behave as documented. Someone sent me an email with this question, and the answer may be useful to others: > but: where is it documented? [ ... ] The 'ext3' filesystem is limited to 8/16TiB: https://ext4.wiki.kernel.org/index.php/Ext4_Howto#Bigger_File_System_and_File_Sizes ?Currently, Ext3 support 16 TiB of maximum file system size and 2 TiB of maximum file size.? (the same information appears in Wikipedia etc.) and this is the 'ext3' mailing list, not the 'ext4' mailing list which is served at another place: https://ext4.wiki.kernel.org/index.php/Mailinglists so I must assume that the original poster was indeed trying to create an 'ext3' filesystem, and this configuration is thus not going to take effect anyhow: > ext4 = { > features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize > auto_64-bit_support = 1 ## ADDED THIS > inode_size = 256 > } It might feel tempting to convert an 'ext3' filesystem to 'ext4' to escape the 8/16TiB limitation, but even for 'ext4' there is a resize limit of less than 8/16TiB if the filesystem initial size was less than 8/16TiB (which it must be if it was initially 'ext3'), because the 'ext4' ondisk layout by default is compatible then with the 'ext3' ondisk layout if possible and thus uses 32b offsets by default: https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Block_Group_Descriptors ?In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the block group descriptor was only 32 bytes long and therefore ends at bg_used_dirs_count_lo. On an ext4 filesystem with the 64bit feature enabled, the block group descriptor expands to the full 64 bytes described below.? http://comments.gmane.org/gmane.comp.file-systems.ext4/33531 It ?It is possible to format a 32-bit filesystem with larger group descriptors using the "-O 64bit" option, but this doesn't happen by default today. Possibly we should start using the 64-byte group descriptors by default for filesystems over, say, 4 TB, so they can be resized beyond 16 TB. It might also be possible to modify resize2fs to change the pgroup descriptor size, but that isn't possible today.? But the original poster reported: >> resize2fs 1.41.14 (22-Dec-2010) and the configuration above is not going to work anyhow as 'e2fsprogs' before 1.42 do not support sizes larger than 8/16TiB for 'ext4' anyhow: https://ext4.wiki.kernel.org/index.php/Ext4_Howto#Bigger_File_System_and_File_Sizes ?Ext4 adds 48-bit block addressing, so it will have 1 EiB[1] of maximum file system size and 16 TiB of maximum file size. [ ... ] NOTE! The code to create file systems bigger than 16 TiB is, at the time of writing this article, not in any stable release of e2fsprogs. It will be in future releases.? http://os1a.cs.columbia.edu/lxr/source/Documentation/filesystems/ext4.txt?v=2.6.32 ?* ability to use filesystems > 16TB (e2fsprogs support not available yet)? http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.42 ?E2fsprogs 1.42 (November 29, 2011) This release of e2fsprogs has support for file systems > 16TB. Online resize requires kernel support which will hopefully be in Linux version 3.2? The above links also appeared in a web search for the phrase "too large to be expressed in 32 bits" which yields some more useful links (for 'ext4'): http://blog.ronnyegner-consulting.de/2011/08/18/ext4-and-the-16-tb-limit-now-solved/ http://forums.debian.net/viewtopic.php?f=5&t=77522 Anyhow I reckon that filesystems significantly larger than 2-6TiB are not a good idea for a number of important reasons, which however matter only when things go wrong, so most people don't care, and that resizing is a somewhat dangerous operation that has performance problems, so overall I would not recommend going looking for trouble... From jayen at jayenashar.org Wed Aug 15 10:16:26 2012 From: jayen at jayenashar.org (Jayen) Date: Wed, 15 Aug 2012 20:16:26 +1000 Subject: bind mounts, chroots, and mismatching kernel with userland Message-ID: <502B76FA.7040508@jayenashar.org> I have a 32-bit debian system, but I recently needed to mmap large files, so I started using a 64-bit kernel with my 32-bit userland and installed a 64-bit debian chroot to run inside. I use bind mounts for proc, sys, tmp, dev, and home. It all works fine, but occasionally, the filesystem gets corrupted (/ and /home are on the same system). I am running linux 3.2.21 (3.2.0-3 in debian). Have I done something I shouldn't do? I hope this is the right mailing list for this question; I couldn't find another linux fs user mailing list. Thanks, Jayen From lists at nerdbynature.de Thu Aug 16 05:15:19 2012 From: lists at nerdbynature.de (Christian Kujau) Date: Wed, 15 Aug 2012 22:15:19 -0700 (PDT) Subject: bind mounts, chroots, and mismatching kernel with userland In-Reply-To: <502B76FA.7040508@jayenashar.org> References: <502B76FA.7040508@jayenashar.org> Message-ID: On Wed, 15 Aug 2012 at 20:16, Jayen wrote: > proc, sys, tmp, dev, and home. It all works fine, but occasionally, the > filesystem gets corrupted (/ and /home are on the same system). I am > running linux 3.2.21 (3.2.0-3 in debian). "Corrupted, as in....?" - Please post error messages, mountoptions and fsck outputs, if attempted. Thanks, Christian. -- BOFH excuse #116: the real ttys became pseudo ttys and vice-versa. From jayen at jayenashar.org Thu Aug 16 07:19:27 2012 From: jayen at jayenashar.org (Jayen) Date: Thu, 16 Aug 2012 17:19:27 +1000 Subject: bind mounts, chroots, and mismatching kernel with userland In-Reply-To: References: <502B76FA.7040508@jayenashar.org> Message-ID: <502C9EFF.10606@jayenashar.org> Corrupted, as in /boot disappeared once and fsck reports heaps of errors. (fsck did not successfully find /boot that time, and only found one initrd (out of 3), no kernels). i don't have any error messages at the moment (because the disk becomes read only), but i'll take a picture next time it happens. is there any way to record the fsck output to a text file if it's running from the drive itself? mount options: /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) tmpfs on /home/jayen/pkg/64/tmp type tmpfs (rw,nosuid,nodev,relatime,size=814512k) /dev/sda1 on /home/jayen/pkg/64/home type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) proc on /home/jayen/pkg/64/proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /home/jayen/pkg/64/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=213489,mode=755) sysfs on /home/jayen/pkg/64/sys type sysfs (rw,nosuid,nodev,noexec,relatime) fstab: proc /proc proc defaults 0 0 UUID=2b04563a-22b9-4b8a-b7c3-98774b749d7e / ext4 errors=remount-ro,noatime,discard 0 1 /tmp /home/jayen/pkg/64/tmp bind defaults,bind 0 0 /home /home/jayen/pkg/64/home bind defaults,bind 0 0 /proc /home/jayen/pkg/64/proc bind defaults,bind 0 0 /dev /home/jayen/pkg/64/dev bind defaults,bind 0 0 /sys /home/jayen/pkg/64/sys bind defaults,bind 0 0 Thanks, Jayen On 16/08/12 15:15, Christian Kujau wrote: > On Wed, 15 Aug 2012 at 20:16, Jayen wrote: >> proc, sys, tmp, dev, and home. It all works fine, but occasionally, the >> filesystem gets corrupted (/ and /home are on the same system). I am >> running linux 3.2.21 (3.2.0-3 in debian). > > "Corrupted, as in....?" - Please post error messages, mountoptions and > fsck outputs, if attempted. > > Thanks, > Christian. > From bruno at wolff.to Thu Aug 16 12:48:18 2012 From: bruno at wolff.to (Bruno Wolff III) Date: Thu, 16 Aug 2012 07:48:18 -0500 Subject: bind mounts, chroots, and mismatching kernel with userland In-Reply-To: <502C9EFF.10606@jayenashar.org> References: <502B76FA.7040508@jayenashar.org> <502C9EFF.10606@jayenashar.org> Message-ID: <20120816124818.GB14380@wolff.to> On Thu, Aug 16, 2012 at 17:19:27 +1000, Jayen wrote: > >i don't have any error messages at the moment (because the disk becomes >read only), but i'll take a picture next time it happens. is there any >way to record the fsck output to a text file if it's running from the >drive itself? Some options are using a removable drive or netconsole. From jayen at jayenashar.org Thu Aug 23 04:01:55 2012 From: jayen at jayenashar.org (Jayen Ashar) Date: Thu, 23 Aug 2012 14:01:55 +1000 Subject: bind mounts, chroots, and mismatching kernel with userland In-Reply-To: <20120816124818.GB14380@wolff.to> References: <502B76FA.7040508@jayenashar.org> <502C9EFF.10606@jayenashar.org> <20120816124818.GB14380@wolff.to> Message-ID: Thanks for your assistance. dmesg output: [609652.499426] EXT4-fs error (device sda1): ext4_mb_generate_buddy:739: group 329, 19 clusters in bitmap, 0 in gd [609652.499433] Aborting journal on device sda1-8. [609652.499536] EXT4-fs (sda1): Remounting filesystem read-only [609652.499545] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4475: Journal has aborted [609652.499638] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4475: Journal has aborted [609652.499731] EXT4-fs error (device sda1) in ext4_ext_remove_space:2637: Journal has aborted [609652.499822] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4475: Journal has aborted [609652.499912] EXT4-fs error (device sda1) in ext4_ext_truncate:4251: Journal has aborted [609652.500037] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4475: Journal has aborted [609652.500141] EXT4-fs error (device sda1) in ext4_orphan_del:2115: Journal has aborted [609652.500323] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4475: Journal has aborted fsck output attached. mount options: /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) tmpfs on /home/jayen/pkg/64/tmp type tmpfs (rw,nosuid,nodev,relatime,size=814512k) /dev/sda1 on /home/jayen/pkg/64/home type ext4 (rw,noatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,discard) proc on /home/jayen/pkg/64/proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /home/jayen/pkg/64/dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=213489,mode=755) sysfs on /home/jayen/pkg/64/sys type sysfs (rw,nosuid,nodev,noexec,relatime) fstab: proc /proc proc defaults 0 0 UUID=2b04563a-22b9-4b8a-b7c3-98774b749d7e / ext4 errors=remount-ro,noatime,discard 0 1 /tmp /home/jayen/pkg/64/tmp bind defaults,bind 0 0 /home /home/jayen/pkg/64/home bind defaults,bind 0 0 /proc /home/jayen/pkg/64/proc bind defaults,bind 0 0 /dev /home/jayen/pkg/64/dev bind defaults,bind 0 0 /sys /home/jayen/pkg/64/sys bind defaults,bind 0 0 Thanks, Jayen On 16/08/12 22:48, Bruno Wolff III wrote: > On Thu, Aug 16, 2012 at 17:19:27 +1000, > Jayen wrote: >> >> i don't have any error messages at the moment (because the disk becomes >> read only), but i'll take a picture next time it happens. is there any >> way to record the fsck output to a text file if it's running from the >> drive itself? > > Some options are using a removable drive or netconsole. -------------- next part -------------- fsck from util-linux 2.20.1 /dev/sda1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found. Fix? yes Inode 1318990 was part of the orphaned inode list. FIXED. Inode 1319060 was part of the orphaned inode list. FIXED. Inode 2369258 was part of the orphaned inode list. FIXED. Inode 2369315 was part of the orphaned inode list. FIXED. Inode 2369316 was part of the orphaned inode list. FIXED. Inode 2369318 was part of the orphaned inode list. FIXED. Inode 2369319 was part of the orphaned inode list. FIXED. Inode 2369322 was part of the orphaned inode list. FIXED. Inode 2369323 was part of the orphaned inode list. FIXED. Inode 2369325 was part of the orphaned inode list. FIXED. Inode 2369327 was part of the orphaned inode list. FIXED. Inode 2369328 was part of the orphaned inode list. FIXED. Inode 2369332 was part of the orphaned inode list. FIXED. Inode 2369333 was part of the orphaned inode list. FIXED. Inode 2369334 was part of the orphaned inode list. FIXED. Inode 2369336 was part of the orphaned inode list. FIXED. Inode 2369337 was part of the orphaned inode list. FIXED. Inode 2369338 was part of the orphaned inode list. FIXED. Inode 2369339 was part of the orphaned inode list. FIXED. Inode 2369341 was part of the orphaned inode list. FIXED. Inode 2369342 was part of the orphaned inode list. FIXED. Inode 2369344 was part of the orphaned inode list. FIXED. Inode 2369345 was part of the orphaned inode list. FIXED. Inode 2369346 was part of the orphaned inode list. FIXED. Inode 2369348 was part of the orphaned inode list. FIXED. Inode 2369349 was part of the orphaned inode list. FIXED. Inode 2369350 was part of the orphaned inode list. FIXED. Inode 2369352 was part of the orphaned inode list. FIXED. Inode 2369353 was part of the orphaned inode list. FIXED. Inode 2369354 was part of the orphaned inode list. FIXED. Inode 2369355 was part of the orphaned inode list. FIXED. Inode 2369356 was part of the orphaned inode list. FIXED. Inode 2369360 was part of the orphaned inode list. FIXED. Inode 2369361 was part of the orphaned inode list. FIXED. Inode 2369363 was part of the orphaned inode list. FIXED. Inode 2369364 was part of the orphaned inode list. FIXED. Inode 2369365 was part of the orphaned inode list. FIXED. Inode 2369366 was part of the orphaned inode list. FIXED. Deleted inode 2375966 has zero dtime. Fix? yes Inode 3321328 was part of the orphaned inode list. FIXED. Inode 3321333 was part of the orphaned inode list. FIXED. Inode 3321335 was part of the orphaned inode list. FIXED. Inode 3321337 was part of the orphaned inode list. FIXED. Inode 3321339 was part of the orphaned inode list. FIXED. Inode 3321343 was part of the orphaned inode list. FIXED. Inode 3321348 was part of the orphaned inode list. FIXED. Inode 3321349 was part of the orphaned inode list. FIXED. Inode 3321351 was part of the orphaned inode list. FIXED. Inode 3321355 was part of the orphaned inode list. FIXED. Inode 3321357 was part of the orphaned inode list. FIXED. Inode 3321365 was part of the orphaned inode list. FIXED. Inode 3321367 was part of the orphaned inode list. FIXED. Inode 3321412 was part of the orphaned inode list. FIXED. Inode 3321533 was part of the orphaned inode list. FIXED. Inode 3321554 was part of the orphaned inode list. FIXED. Inode 3321631 was part of the orphaned inode list. FIXED. Inode 3323447 was part of the orphaned inode list. FIXED. Inode 3323449 was part of the orphaned inode list. FIXED. Inode 3323767 was part of the orphaned inode list. FIXED. Inode 3323768 was part of the orphaned inode list. FIXED. Inode 3323769 was part of the orphaned inode list. FIXED. Inode 3323770 was part of the orphaned inode list. FIXED. Inode 3323771 was part of the orphaned inode list. FIXED. Inode 3323772 was part of the orphaned inode list. FIXED. Inode 3323773 was part of the orphaned inode list. FIXED. Inode 3323774 was part of the orphaned inode list. FIXED. Inode 3323775 was part of the orphaned inode list. FIXED. Inode 3434204 was part of the orphaned inode list. FIXED. Inode 3434206 was part of the orphaned inode list. FIXED. Inode 3434207 was part of the orphaned inode list. FIXED. Inode 3434208 was part of the orphaned inode list. FIXED. Inode 3434213 was part of the orphaned inode list. FIXED. Inode 3434215 was part of the orphaned inode list. FIXED. Inode 3434216 was part of the orphaned inode list. FIXED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: -(5668365--5668381) -(5695376--5695384) -9473937 -(10440704--10443488) -(10633207--10633215) -(10645232--10645233) -(10645235--10645240) -(10645304--10645348) -(10645350--10645363) -(10645365--10645368) -(10645370--10645383) -(10645385--10645394) -(10645409--10645416) -(10645418--10645421) -(10645423--10645429) -(10645449--10645463) -(10645466--10645471) -(10677389--10677407) +10789507 +10789593 +10789805 +10789856 +10789878 +10789907 +10790324 +10790510 +10790563 +10790889 +10790907 +10791394 +10791752 +10791809 +10791815 +10792378 +10792445 +10792467 +10792822 -(10826700--10827300) -(13606912--13608256) -(13608911--13609803) -(13610048--13610111) -(13610392--13611486) -(13613249--13613496) -(13619584--13620296) -(13620549--13622325) -(13622884--13623206) -(13623208--13623293) -(13629362--13629414) -(13647169--13647344) -(13647857--13648994) -(13823110--13823195) -(13826002--13826011) -(13826016--13826057) -(13826064--13826078) -(13828432--13828874) -(14559179--14559343) -(14559494--14559904) -(14560501--14560577) -(14560636--14560777) Fix? yes Free blocks count wrong for group #172 (0, counted=17). Fix? yes Free blocks count wrong for group #173 (2418, counted=2427). Fix? yes Free blocks count wrong for group #289 (0, counted=1). Fix? yes Free blocks count wrong for group #318 (32, counted=2817). Fix? yes Free blocks count wrong for group #324 (0, counted=144). Fix? yes Free blocks count wrong for group #325 (780, counted=799). Fix? yes Free blocks count wrong for group #330 (186, counted=787). Fix? yes Free blocks count wrong for group #415 (16, counted=6613). Fix? yes Free blocks count wrong for group #416 (16, counted=1330). Fix? yes Free blocks count wrong for group #421 (0, counted=153). Fix? yes Free blocks count wrong for group #422 (0, counted=443). Fix? yes Free blocks count wrong for group #444 (0, counted=795). Fix? yes Free blocks count wrong (788752, counted=801630). Fix? yes Inode bitmap differences: -1318990 -1319060 -2369258 -(2369315--2369316) -(2369318--2369319) -(2369322--2369323) -2369325 -(2369327--2369328) -(2369332--2369334) -(2369336--2369339) -(2369341--2369342) -(2369344--2369346) -(2369348--2369350) -(2369352--2369356) -(2369360--2369361) -(2369363--2369366) -2375966 -3321328 -3321333 -3321335 -3321337 -3321339 -3321343 -(3321348--3321349) -3321351 -3321355 -3321357 -3321365 -3321367 -3321412 -3321533 -3321554 -3321631 -3323447 -3323449 -(3323767--3323775) -3434204 -(3434206--3434208) -3434213 -(3434215--3434216) Fix? yes Free inodes count wrong for group #161 (1494, counted=1496). Fix? yes Free inodes count wrong for group #289 (1, counted=37). Fix? yes Free inodes count wrong for group #290 (0, counted=1). Fix? yes Free inodes count wrong for group #405 (149, counted=177). Fix? yes Free inodes count wrong for group #419 (0, counted=7). Fix? yes Free inodes count wrong (3190789, counted=3190863). Fix? yes /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda1: ***** REBOOT LINUX ***** /dev/sda1: 716721/3907584 files (0.2% non-contiguous), 14827599/15629229 blocks