From owner-freebsd-questions Fri Jul 27 6:39:39 2001 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144]) by hub.freebsd.org (Postfix) with SMTP id 4043A37B403 for ; Fri, 27 Jul 2001 06:39:35 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 64347 invoked by uid 100); 27 Jul 2001 13:39:34 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15201.28438.702793.700691@guru.mired.org> Date: Fri, 27 Jul 2001 08:39:34 -0500 To: "Ted Mittelstaedt" Cc: questions@freebsd.org Subject: RE: i-node problems In-Reply-To: <114129392@toto.iv> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ted Mittelstaedt types: > Very little as long as your system doesen't routinely crash. > > /var and /usr are kept separate because one of the things people > have learned over time is that if a filesystem is in the middle of > being written and the system crashes, then the filesystem has more of a > chance of developing errors that fsck cannot repair than if the > filesystem was totally quiescent. So the thought is that if you have > a large /usr with a lot of installed staff and the system falls over > on it's face and /var gets scrambled, then so what, you just newfs it and > restore from the last backup - short and sweet and little time lost. > By contrast if /usr goes down and you have a couple gigs of data in it... > > But I've done exactly what you have done on some systems before for > the same reason with no problems. Two things have changed since the days when that was standard that make this less of a problem. One is that the filesystems are much more robust. The only time I've gotten a badly screwed file system in the last five years was when a power went out three times in a short period, the second two catching the system fscking it's file systems. The other is that instead of being a timesharing system with tens or hundreds of people logged in at once, you see a lot of single-user systems. The value of the time lost fixing a broken file system is much more expensive than in the latter case. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message