[Gllug] ext3 filesystem suddenly full

Nix nix at esperi.org.uk
Fri Jun 22 19:47:54 UTC 2007

On 22 Jun 2007, Jason Clifford verbalised:

> On Fri, 22 Jun 2007, - Tethys wrote:
>> I'd also put /usr on a separate filesystem. That way you can mount it
>> readonly.
> My preferred filesystem layout runs as follows:
> /		512M
> /usr		4GB
> /tmp		256-512M
> /var		10GB
> /var/log	10-50GB depending upon server purpose

Wow. A *minimum* of 10Gb for /var and /var/log? Surely only fairly large
servers need that sort of room...

(and why is /tmp given space on the physical disk at all? tmpfs it!)

Personally I've found 200Mb to be way more than enough for /; I could
probably survive with a 50Mb / but it would be tight. With / being
loaded off LVM(-on-RAID) and with online resizing in the upstream kernel
it's not as hard as it used to be to resize / without any downtime.

> This way there is plenty of space for applications, etc and user data is 
> properly segregated. It also means that 1 filesystem filling will not 
> cause problems for the system beyond that particular filesystem.

This latter point has saved my bacon repeatedly.

> I always segregate / and have nothing other then /etc /bin and /sbin on 
> it.

How do you boot without /lib? ;)

> I remain shocked that distros still offer a single partition solution by 
> default. I just don't think it is ever appropriate.

It's appropriate on very small systems: one box I use regularly has less
than 80Mb available. Cutting that up seems pointless.

`... in the sense that dragons logically follow evolution so they would
 be able to wield metal.' --- Kenneth Eng's colourless green ideas sleep
Gllug mailing list  -  Gllug at gllug.org.uk

More information about the GLLUG mailing list