Its great if a user floods /tmp and you email system wont accept email anymore
because the /var/spool/mail and /var/spool/mqueue is full.
> My resason for this is mainly (KISS). I have come by HP and AIX boxes that have
> actually crashed beacuse the people who did the original installation did to slim
> / and /usr or whatever partitions.
See your statement above - You declare HP and AIX unreliable which is the
opposite of what i feel like working with both. I like the way AIX asks me
to grow /usr automatically on software installation e.g. through smit.
> The need for growing and shrinking partitions on HP and AIX seems to stem from
> this philosophy of makin a lot of filesystems and making them slim so we have a
> lot of free space to grow in.... And yes I know AIX has an autogrow feature but
> this only pushes the problem of full filesystems to the limit where your disks
> are full. Its no better than having all free space in the existing root
> filesystem. Actually it's worse since you go out of disk sooner since the free
> space in the other partitions can't be usen or is there an autoshrink feature
> also.
I am not a fan of enabling "autogrow" all the time but IF a filesystem gets
full i want to be ABLE to grow it or even spread on another hot plugged hd
added to my VG.
> What wrong with having a big / partition with lots of free space to grow in. And
> leave the fragmentation/quota issues to the filesystem implementation.
What do you do if you would like to give a user 30MB in /home and 100MB for
/var/spool/mail ... no way of doing this in a single filesystem with quota.
Flo
-- Florian.Lohoff@mediaWays.net +49-5241-80-7085 Good, Fast, Cheap: Pick any two (you can't have all three). (RFC 1925)- 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/