Date: Tue, 15 Jul 2003 17:20:06 +0100 From: David Malone <dwmalone@maths.tcd.ie> To: Sumit Shah <shah@ucla.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: RAID and NFS exports (Possible Data Corruption) Message-ID: <20030715162006.GA47687@walton.maths.tcd.ie> In-Reply-To: <EEA0280E-B6C7-11D7-9819-000393DB86CA@ucla.edu> References: <EEA0280E-B6C7-11D7-9819-000393DB86CA@ucla.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 15, 2003 at 06:26:24AM -0700, Sumit Shah wrote: > Here is a message I sent to freebsd-questions and I was hoping I could > get some help debugging this. It seems very unlikely that restarting mountd cound cause an error like: >ad4: hard error reading fsbn 242727552 The error means that that the disk said that there was an error trying to read this block. You say that when you rebooted that the controler said a disk had gone bad, so this would sort of confirm this. (I could believe that restarting mountd might upset raid stuff if there were a kernel bug, but it seems very unlikely it could cause a disk to go bad.) My best guess would be that you have a bad batch of disks that happen to have failed in similar ways. It is possible that restarting mountd uncovered the errors, 'cos I think mountd internally does a remount of the filesystem in question and that might cause a chunk of stuff to be flushed out on to the disk, highlighting an error. (I had a bunch of the IBM "deathstar" disks fail on me within the space of a week or so, after they'd been in use for about six months.) David.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030715162006.GA47687>