Date: Tue, 17 Nov 2015 18:01:55 +0100 From: Gerhard Schmidt <schmidt@ze.tum.de> To: Adam Vande More <amvandemore@gmail.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Random Lockup with FreeBSD 10.2 on SuperMicro Boards Message-ID: <564B5D83.5000909@ze.tum.de> In-Reply-To: <CA%2BtpaK3065Tw_NC=VXa0Pq3ZD_mXUcHhvoVrSOw8feHr7i5gaw@mail.gmail.com> References: <56498205.3060806@ze.tum.de> <20151116094334.GS2604@mordor.lan> <5649A761.7040303@ze.tum.de> <20151116111609.a9757a4a.freebsd@edvax.de> <5649AEC3.5090104@ze.tum.de> <20151116164507.GA87691@neutralgood.org> <CA%2BtpaK3065Tw_NC=VXa0Pq3ZD_mXUcHhvoVrSOw8feHr7i5gaw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 17.11.2015 17:23, schrieb Adam Vande More: > On Mon, Nov 16, 2015 at 10:45 AM, <kpneal@pobox.com > <mailto:kpneal@pobox.com>> wrote: > > When in doubt use 'fsck -f' to force a check despite the filesystem > being marked clean. > > > Yes, but a full fsck should be run on a regular basis regardless of > suspicion. > > Personally, I got bit by SU (plain) a long time ago and I've never > really > trusted it since. I strongly advise you to 'fsck -f' on your /var > just to > rule out _any_ corruption there. > > > A lower level fs error isn't going be to detected by a background > fsck(only does preening) or SUJ fsck(trusts the journal). Such errors > can occur on *any* journaled fs. Periodically doing a full fsck on fs's > is actually something Linux does better. > > https://lists.freebsd.org/pipermail/freebsd-current/2013-July/042951.html > > Many think SU or SUJ obviate the need for a periodic full fsck. It does > not. SU and SUJ devs have repeated this since their respective > inception. [1] Hardware still lies, bitrot still occurs, do a full > fsck. Vague reports of "I don't trust this" aren't helpful. If you > know of a bug, please report it so it can be addressed. > > [1] > https://lists.freebsd.org/pipermail/freebsd-arch/2010-January/009872.html -- > Well initially it's claimed "eliminate fsck after an unclean shutdown" > but details it later showing fsck using journal isn't a full fsck. Let's get back to Topic. There is no corruption. And still if there is that's software bug and has to be fixed. This is not biology where something happens spontaneously. This is computer science. If there is something wrong there are only three explanations. The User done something wrong, not likely here. There is an Hardware error, on three different Servers roughly after the same amount of time not very likely either. So it's cause number three: Bug in the Software. As I said. I have 76 Servers running FreeBSD (various versions from 8.4 to 10.2) only 3 of them are 10.2 (5 since yesterday) and of this three running 10.2 longer than a month 100% had this Problem at least once. out of the 73 other servers 0% had this Problem and 45 of them are the exact same Hardware and all of them running considerably longer than one Month. And for the fscks. The last time i had to do a fsck on any partition, beside Hardware failures, was about 2 and 1/2 years ago when your UPS died and killed the power. And besides from some logfiles even than there was no corruption. I have filesystems that are 8 years without a fsck, that are production servers. I have never had problems with UFS SU and UFS SU-J. Sorry guys there is no problem with UFS on FreeBSD. I agree if there is an unclean shutdown you might want to do an complete fsck. But in the case discussed here the unclean shutdown was an result of the lockup not the other way round. Regards Estartu - -- - ------------------------------------------------- Gerhard Schmidt | E-Mail and JabberID: TU-München | schmidt@ze.tum.de WWW & Online Services | PGP-Publickey on Request -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJWS12DAAoJEHTSQ8xFcA2j2I0P/24+QctZ6m2uPWs8QjHGyAs9 yV/wNargEtE7Uu6iOupdZVxKyycPPLPaFWyylMBbBGacqBIZVq3W9M1Hu2doS86W Ou3QVOco5fkPqntUEIzdaFGfLE196ZpifP+8nZsmwad/kdjSxpPSetLIsyIv4GbE qhdcEHHfgXqposB/2dt7E/52TuyLRuHBZG0bE3Wpevlc4YTaLt5cvDhMLDlPUu/c 8bynd1DDaA+89N5Y0FSgpUOb+xSKzYs4xGD/rWxOxniuzhRnSLaX8AY22B/apbin knBi0dctNiT8Vrdd6ycJHVO3FvtfWW5ETvYEEnDFe87sEwsyHMlQ1mj5SqMdYpdj hoD928L9qNATmpNxMbr+2PrvtFvDmoeC8X8J/8iGmLVB1+IQf4mIYMjbSyGYYxbg yA0bhsJEr+sjq/L7+DTGDJqmQ5ixck/BFJ7iKbQEVyR3OnRhAp0SBjyMvH1LoPFg e9f4bux1OOCu3IRwMbxIPoioIOwyHYwrH6WmkM4TMHGjfDL9EeDE+Jp9F0+gLbyF T/9gtgNcBWvgCxyqzAqESW7/A6qV9P+AzY5oyggimjwRpMO4H85ZBTlgQEN6SsCR utDtyBQtBO15RgtqL21eNtS9QWDrHgB56+3FdWEuT2ipq9R+7kehNgsfNZJqLXHs MxRlqHb451cjsKgzIt3E =TdfF -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564B5D83.5000909>