Date: Wed, 22 Jun 2022 09:52:43 +0200 From: Eivind Nicolay Evensen <eivinde@terraplane.org> To: Andy Farkas <andyf@andyit.com.au> Cc: Mr Roooster <mrrooster@gmail.com>, stable@freebsd.org Subject: Re: Unclean file systems on every boot Message-ID: <20220622095243.0aadceb3@elg.hjerdalen.lokalnett> In-Reply-To: <9b5fb5d9-c8f4-3073-65dd-3c1cff603ec5@andyit.com.au> References: <20220616162939.614bcd4b@elg.hjerdalen.lokalnett> <YquRc%2B5LvHyiYDF3@elch.exwg.net> <CAJVtfJTg08GF3NFn55sE_BMfd13u4ySpa-QPVa%2B69SYG9J0dPw@mail.gmail.com> <9b5fb5d9-c8f4-3073-65dd-3c1cff603ec5@andyit.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Den Mon, 20 Jun 2022 03:06:49 +1000 skrev Andy Farkas <andyf@andyit.com.au>: > On 19/06/2022 10:27 pm, Mr Roooster wrote: > > > ... running a memtest for a day isn't a bad shout. > > Indeed. Ran memtest on a system I was never happy with, > it did 3 complete passes without incident, then on pass 4 > it found a bit-flip. I may just try that at a time when I don't need the machine. I do think that if this turned out to be memory issues, I'd be amused rather than irritated that the result of it was dirty file systems only on one out of four disks, only started after I replaced an older disk with real problems with this one and that fsck never actually find anything to correct. -- Eivind Nicolay Evensen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220622095243.0aadceb3>