Date: Sat, 25 Jul 2015 18:30:38 +0200 From: CeDeROM <cederom@tlen.pl> To: CK <nibbana@gmx.us> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: Endless Data Loss Message-ID: <CAFYkXjknSK=%2BnpPg67vpLwtYJRRdHFmX=Jxp%2BCGGZcTHq3%2BGxQ@mail.gmail.com> In-Reply-To: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com> References: <0MRCCJ-1ZUCcr1rAt-00UeQk@mail.gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
UFS2 SU+J has failed me several times as well. I also ocassionaly experienced root filesystem corruption that prevented valid boot. Even on a fresh install and new hardware I consider UFS2 SU+J unreliable.. I am not sure why this got into production :-( Performing forced fsck on a SU+J filesystem that was considered clean in J revealed inconsistency on fsck. Try to disable SU+J, maybe only J as mentioned in other reply. I will try that too. Try ZFS for good consistency. Or wait/force full fsck before system is up. Also, take a look at hard drive details - manufacturer and series (i.e. WD RED, BLACK, GREEN) - they can have totally different firmware with badblock correction that may cause troubles as well. Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjknSK=%2BnpPg67vpLwtYJRRdHFmX=Jxp%2BCGGZcTHq3%2BGxQ>