Date: Sat, 30 Sep 2006 17:15:06 -0700 From: Cy Schubert <Cy.Schubert@spqr.komquats.com> To: "Vlad GALU" <dudu@dudu.ro> Cc: freebsd-stable@freebsd.org Subject: Re: Frequent VFS crashes with RELENG_6 Message-ID: <200610010015.k910F6Ba001594@cwsys.cwsent.com> In-Reply-To: Message from "Vlad GALU" <dudu@dudu.ro> of "Sat, 30 Sep 2006 19:01:01 %2B0300." <ad79ad6b0609300901q4215c809ye28fd861007494da@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <ad79ad6b0609300901q4215c809ye28fd861007494da@mail.gmail.com>, "Vlad GALU" writes: > On 9/30/06, Martin Blapp <mb@imp.ch> wrote: > > > > Hi, > > > > 1.) Bad ram ? Have you run some memory tester ? > > Yes, memtest86 didn't show anything weird. > > > 2.) Have you background fsck running on this disk ? If > > so try to boot into single user and do a full fsck on this > > disk. > > > > I have background_fsck="NO" in rc.conf and I checked the whole disk > several times. > Something I forgot to mention earlier: the crash is easier to > reproduce when running rtorrent. The machine did crash without running > it as well, but far more seldom. I've been experiencing the same problem as well. I discovered that the disk on which the filesystem was had some bad sectors causing dump -0Lauf to fail while taking snapshot causing the system to panic. Running smartctl on the device indicated that there were bad sectors 40% within the surface scan being performed by SMART. The drive, an 80 GB Maxtor, was replaced with a 250 GB Western Digital (for a very good price, so good a price I purchased two of them). It was 906 days old, having only been powered off maybe a dozen times over the last three years. -- Cheers, Cy Schubert <Cy.Schubert@komquats.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org e**(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610010015.k910F6Ba001594>