Peter Marelas wrote:
> I guess the other issue is how long is it going to take to fsck large
> dirty filesystems. It amounts to downtime.
>
> But, regardless, a user is generally not required if you modify your
> run level start script to force fsck with -y.
For automated caches it is probably more suitable to newfs a cache disk
if a normal fsck fails. It is hard to tell what errors that may occur
or how long time a fsck -y takes.
* newfs is always quicker than fsck on a dirty filesystem.
* newfs leaves the filesystem in a well known state (empty).
* cache data is non-critical.
--- Henrik Nordström Sparetime Squid HackerReceived on Tue Sep 15 1998 - 21:14:37 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:02 MST