[NTLUG:Discuss] Re: Strange Request, Maybe?

[cbbrowne@hex.net]

On Thu, 10 May 2001 08:50:30 CDT, the world broke into rejoicing as
Bug Hunter <bughuntr at one.ctelcom.net>  said:
> On Wed, 9 May 2001, Chris Cox wrote:
> 
> > Will Senn wrote:
> > ... 
> > > I don't pretend to understand the internals of any filesystem,
> > > however, I have certainly had my share of filesystem issues in linux
> > > from unexpected power loss.
> > 
> > THIS had NOTHING to do with power loss... I think you missed
> > the point... NT crashed and failed to reboot successfully at ALL.
> > No startup screen, no nothing.... was not due to a power loss,
> > happened after getting a BSOD.
> > 
> > As I mentioned, both filesystems will exhibit abnormal behavior
> > in certain circumstances on power hits.  ext2 could be more
> > susceptible strictly because of how it buffers things... where
> > NT has an all-or-nothing style (heavy cache, heavy write).
> <snip>
 
> If you are paranoid about power loss problems, put a cron job that
> runs /bin/sync once every 5 minutes.

> After doing this, we have not yet had an ext2 drive fail to
> automatically fsck during boot up without human intervention.
> Before this, about 1 of 3 power ups required human intervention.

... And note that ReiserFS is now in the "official" kernel tree,
suggesting that it is possibly approaching usability.  It further
diminishes the likelihood of needing to have manual intervention.

And has the further advantage that the "fsck equivalent" is guaranteed
to run in seconds, whereas an fsck of a large ext2 filesystem can run
for minutes, or even hours, in pathological cases...
--
(reverse (concatenate 'string "ac.notelrac.teneerf@" "454aa"))
http://www.ntlug.org/~cbbrowne/resume.html
"Rules of Optimization:
     Rule 1: Don't do it.
     Rule 2 (for experts only): Don't do it yet."
-- M.A. Jackson