Lowell Gilbert wrote:
Heinrich Rebehn [EMAIL PROTECTED] writes:
I have had the above error 2 times now during fsck after an unclean
shutdown. fsck -y yielded tons of entries in lost+found.
man (7) tuning says that softupdates guarantees filesystem consistency
in case of crash, but thousands of
Hi Heinrich Rebehn,
you wrote.
Make sure you've disabled write caching on the drive firmware
itself...
HR Does this also apply for RAID disks (twe)? Also, there is no word about
HR this in man tuning(7). Is this more of a guess or is softupdates
HR definately dangerous with wite cache
Gabriel Ambuehl wrote:
Hello Heinrich,
Sunday, February 22, 2004, 5:00:27 PM, you wrote:
Why that? I can imagine that i lose data in case of a power failure, but
why in case of a crash?
Well I guess the card COULD still commit the data, however, who knows
if it actually does it?
And why is
Hello Heinrich,
Sunday, February 22, 2004, 6:49:46 PM, you wrote:
what you write does make sense, although i really can't understand why
this important info is not in the FreeBSD documentation.
I have disabled write cache, but i will keep softupdates disabled as
well for now, and see how the
Hello Heinrich,
Sunday, February 22, 2004, 5:00:27 PM, you wrote:
Why that? I can imagine that i lose data in case of a power failure, but
why in case of a crash?
Well I guess the card COULD still commit the data, however, who knows
if it actually does it?
And why is write cache only
Hi list,
I have had the above error 2 times now during fsck after an unclean
shutdown. fsck -y yielded tons of entries in lost+found.
man (7) tuning says that softupdates guarantees filesystem consistency
in case of crash, but thousands of lost files tell a different story.
Did i miss anything?
