Date: Mon, 17 Jan 2000 14:23:25 +0000 (GMT)
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> The ext2 mount code defaults to do a full check at mount time, and it
> takes _forever_ on a big disk because the full check involves going
> through every superblock and verifying that they all match etc.
Its caught errors before that probably avoided people losing
data. Its a good sanity check. The "stupid" defaults are two other things
o Using 1K blocks on large disks (4K is way faster) and
4K checks way faster too
o Not using the "sparse superblock" option on large disks
when creating them.
These defaults are changed in e2fsprogs 1.18. Unfortunately Linux 2.0
kernels don't support sparse superblocks. I have patches to allow 2.0
kernels to support sparse superblocks, though. E-mail me if you're
interested.
Unfortunately I dont think there are any "in place" fixers for those
creation time choices
Nope, unfortunately not for blocksizes. If you have an old filesystem
using 1k blocks, you'll have to do a dump/mke2fs/restore pass to change
it to use 4k blocksizes.
If you just want to enables sparse superblocks to get some space back,
you can do that by running "tune2fs -s 1 /dev/XXX", and then running
"e2fsck -f /dev/XXX".
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:17 EST