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 lost files tell a different story. Did i miss anything? Or should i disable softupdates for important data?
Make sure you've disabled write caching on the drive firmware
itself...
Does this also apply for RAID disks (twe)? Also, there is no word about this in man tuning(7). Is this more of a guess or is softupdates definately dangerous with wite cache enabled? I have also used softupdates with 4.9 and did not get these errors.
The system is running FreeBSD 5.2.1-RC2
I hope you have read the Early Adopter's Guide: http://www.freebsd.org/releases/5.2R/early-adopter.html
Yes i have and after asking others on this list, got the impression that 5.2 is usable for the most common hardware and applications. But now i am seriously considering going back to 4.9
Thanks very much for your reply :-)
Heinrich _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
