Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] how filesystem works?
- Date: Mon, 02 Apr 2007 13:51:01 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] how filesystem works?
- References: <20070329090009.GK3981@example.com> <ba75897e0703290433l4c843928pb7a155f123579fbd@example.com> <20070329114843.GL3981@example.com> <460BAF7A.2050905@example.com> <20070330070435.GM3981@example.com> <20070330142231.721fd4d8.attila@example.com> <871wj6y3vl.fsf@example.com> <Pine.NEB.4.64.0704011455570.18091@example.com> <460FD438.3090802@example.com>
Stuart Luppescu writes: > This is something I never understood. Someone told me to put /var in its > own partition because if it fills us (with log files, or whatever) it > will crowd out other stuff and make the computer unusable. That's an inaccurate statement of the advantage. If you do quarantine /var, you can boot to single-user (or simply stop daemons etc that use /var, but that's tricky), find space on another partition, mv (or "gzip >") the logs (mail spool, etc) there, and restart the system. Also, any write operation on another partition will succeed, you won't lose data. If you use a single partition for everything, you don't have that option; you need to either delete stuff, which you probably don't want to do without looking at it, or you have to move it to other media, which is painful (no space means you can't burn CDs). If you happen to be writing a file with many changes and you run out of space, rebooting means you lose all of that. > I did that, and then /var filled up, syslog and cron complained > about not being able to write files and the whole computer froze > up. A freeze shouldn't happen. You'll lose mail service and anything else that spools to disk in /var, but any operation that doesn't write to /var should proceed normally. > Now I put /var inside / and haven't had any problems. Problems are less likely, but if you ever do have problems, you may be in for a world of pain. It's up to you to decide whether that matters. Some people really don't care about their logs, for example, and will be able to just delete the 10GB net log that happened because of a DoS attack. But if you think you might ever need to use your logs in court, consider that that action could cost you the ability to present your logs as evidence: logs are hearsay unless you can show that you manage them properly in the normal course of running your system.[1] Footnotes: [1] IANAL,TINLA. Source: Bellovin and Cheswick, which is now way old.
- Follow-Ups:
- Re: [tlug] how filesystem works?
- From: Darren Cook
- Re: [tlug] how filesystem works?
- From: Godwin Stewart
- Re: [tlug] how filesystem works?
- From: Attila Kinali
- References:
- Re: [tlug] how filesystem works?
- From: Curt Sampson
- Re: [tlug] how filesystem works?
- From: Stuart Luppescu
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] how filesystem works?
- Next by Date: Re: [tlug] how filesystem works?
- Previous by thread: Re: [tlug] how filesystem works?
- Next by thread: Re: [tlug] how filesystem works?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links