Split up /var filesystem into /var/tmp and /var/spool

[KapilRaj]

Guys,

Will you approve my Change Request for implementing the above change on a production node ?.

Some stupid users vi files of 50 MB and my sendmail crashes as it does not have space in /var. hunmmmm i am in trouble. Thought of revmoving "vi" command itself !!!.

Kaps

[Mark Grant]

I see no reason why you can't do this. There are other options though. Like implementing quota's or using a symbolic link from /var/tmp to some area where you have lots of space. If you want to annoy your (ab)users you can allways symbolically link it to /dev/null.

[Kurt Beyers.]

Kaps,

Just create another lvolx and mount it under a temporary subdirectory /tmp_var.

Copy the contents of /var/mail to /tmp_var.

Mount now the lvolx under /var/mail and start sendmail again.

The same procedure can be used for other subdirectories of /var.

This is a convenient method to prevent that /var becomes 100% full as it only can be extended when you boot in single user mode.

best regards,
Kurt

[MarkSyder]

How about giving the users a separate filesystem under /var? /var/morons for example! If it's a separate filesystem it won't intrude on the main /var.

Mark Syder (like the drink but spelt different)

[Sanjay Kumar Suri]

Can have two files systems a. /var and another /var/tmp.

Check out the reason for editing large files. Can you help them from your sysadm experience?

sks

[Pete Randall]

I like Mr. AlmostAlcoholicAppleJuice's idea: /var/morons!!!

At this point, I would have to agree that a separately mounted filesystem is about the only thing you can do. Quotas will end the problem without really fixing it - you'll be dealing with calls from all the users that can't open their large mail messages instead.

Either the symbolic link or Kurt's mount suggestion seem to be just the ticket.


Pete

[KapilRaj]

Have u implemented it ?. Any experience in doing it ?.

Kaps

[Naveej.K.A]

Go on to create another logical volume and mount /var/tmp to that LV....

Or think of adding some more PEs to the LV to get yourself more space for the /var filesystem...

[MarkSyder]

I have implemented separate filesystems under existing filesystems.

It works well and I recommend it.

Mark

[Naveej.K.A · Accepted solution]

yes...
I have seen production systems working with splitted files systems. and its seems to work perfectly fine.
All the best and have a nice weekend
regds
naveej

[KapilRaj]

Thanks Naveej and all those who have replied,

Would go for it; and u r worth those points !

This is a wonderfull place for a sysadmin to be. Nice working with you guys.. Enjoy ur weekend.

Kaps

[Thierry Poels_1]

hi,

we always create separate filesystems for /var/tmp & /var/adm/crash. The primary reason is preventing /var to fill up completely.
Never had problems with /var/spool (remote printing ;) so we leave this in /var.

regards,
Thierry.

[Trond Haugen]

As discussed creating separate lvols ounder /var will work. I see the reason for wanting to pervent users from filling up the filesystem so sendmail stops. Keeping them on their own filesystem will only stop them. But if you want to avoid calls from users having problems vi'ing files you could just increase /var. Of course you could have problems if vi craskes and leaves 50 MB recover files...

Regards,
Trond

[KapilRaj]

This case is closed !

Kaps