On Mon, Jul 31, 2006 at 05:59:58PM +0200, Adrian Ulrich wrote:-Hello Matthias,This case is solvable by planning. When you know that the new fs
This looks rather like an education issue rather than a technical limit.
We aren't talking about the same issue: I was asking to do it
on-the-fly. Umounting the filesystem, running e2fsck and resize2fs
is something different ;-)
Which is untrue at least for Solaris, which allows resizing a life file
system. FreeBSD and Linux require an unmount.
Correct: You can add more inodes to a Solaris UFS on-the-fly if you are
lucky enough to have some free space available.
A colleague of mine happened to create a ~300gb filesystem and started
to migrate Mailboxes (Maildir-style format = many small files (1-3kb))
to the new LUN. At about 70% the filesystem ran out of inodes; Not a
big deal with VxFS because such a problem is fixable within seconds.
What would have happened if he had used UFS? mkfs -G wouldn't work
because he had no additional Diskspace left... *ouch*..
must be created with all inodes from the start, simply count
how many you need before migration. (And add a decent safety margin.)
That's what I do with my home machine ask disks wear out every third
year or so. The tools for ext2/3 tells how many inodes are in use,
and the new fs can be made accordingly. The approach works for bigger
machines too of course.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/