Re: Corrupted files on 2.4.18.

[Austin Gonyou <austin@coremetrics.com>]

does anyone know how much speed is lost by osync?

On Wed, 2002-03-20 at 12:32, Juri Haberland wrote:
> Daniel Fonseca wrote:
> > Hi Eric!
> > 
> > Don't you think that this is a major nuisance? I mean, I am very glad
> > with XFS on the server level, but at my home machine I have ext3 and
> xfs
> > (using, testing and comparison purposes) and everytime there's a hard
> > reset (too many times lately, unfortunately) only the files on the xfs
> > partition get this "screwed". Ext3 truncates (or whatever) them, but
> > loosing the whole files is very bad on the user's point of view -
> > configuration files, for example, drove my client applications mad to
> > the point that I removed xfs completely, to avoid this. Enabling and
> > pressing the Magic SysRq key and flushing out is not a clean solution,
> > IMHO.
> > 
> > I seem to remember this being a bug reported some time ago, and
> thought
> > it was corrected, though.
> 
> Hmm, hmm, IMO it's not a bug, but a feature ;) If you want your data
> reliable on disk mount it -osync. That's what I do on partitions where I
> won't risk running into this "zero"-issue. Oh well, I think we all are a
> bit pampered (right word? please correct me) by ext3 :-)
> 
> > It's never enough to say how great your job has been for all of us!
> 
> Yes, indeed!
> 
> Juri
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb