lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 14 Nov 2012 03:07:24 +0200 (EET) From: Kimmo Mustonen <k-20121112-81452+linux-ext4@...mmola.net> To: Theodore Ts'o <tytso@....edu> cc: Kimmo Mustonen <k-20121112-81452+linux-ext4@...mmola.net>, linux-ext4@...r.kernel.org Subject: Re: resize2fs running out of reserved gdt blocks. On Mon, 12 Nov 2012, Theodore Ts'o wrote: > If you are willing to temporarily boot a bleeding edge 3.7 kernel and > use the resize2fs from e2fsprogs 1.42.6, you'll be able to resizing > your partition. After you do this, you could fall back to the Debian After a bit of fighting generating a proper .config file I managed to boot into 3.7.0-rc5 and resize the partition. And I just noticed that I accidentally used e2fsprogs 1.42.5 for doing that. Should I be worried about that? Now back running 3.2.0-0.bpo.3-amd64 kernel. I'm running e2fsck-1.42.6 to check it now. BTW, resize from 12T to 15T was amazingly fast (about 30 seconds) now when comparing to the "old" behaviour where it took hours to complete. Thanks! > stable kernel and things should work w/o problems; the latest kernel > and e2fsprogs code is needed just for the online resize operation. If I continue to increase the array using 3.7.0-rc5 and resize2fs-1.42.6, when do you expect me to encounter problems or hit the next barrier? Is going past 16TB safe? How about 32TB? What is the maximum size I can reach with this setup? The filesystem was made with 64bit flag. Regards, Kimmo -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists