linux-kernel - Re: MD/RAID time out writing superblock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 14 Sep 2009 15:13:33 -0600
From:	Thomas Fjellstrom <tfjellstrom@...w.ca>
To:	linux-kernel@...r.kernel.org
Cc:	Tejun Heo <tj@...nel.org>, Chris Webb <chris@...chsys.com>,
	linux-scsi@...r.kernel.org, Ric Wheeler <rwheeler@...hat.com>,
	Andrei Tanas <andrei@...as.ca>, NeilBrown <neilb@...e.de>,
	"IDE/ATA development list" <linux-ide@...r.kernel.org>,
	Jeff Garzik <jgarzik@...hat.com>, Mark Lord <mlord@...ox.com>
Subject: Re: MD/RAID time out writing superblock

On Mon September 14 2009, Tejun Heo wrote:
> Hello,
> 
> Thomas Fjellstrom wrote:
> > I have the same issue with a single WD 2TB Green drive. Technically two,
> > but it always only gets errors from the same drive, so I was assuming it
> > was the drive. I only have to setup the raid0 array, and put some light
> > load on it for the kernel to start complaining, and eventually it just
> > kicks the drive completely with the following messages:
> >
> > sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> > end_request: I/O error, dev sdb, sector 202026972
> >
> > The drive does work fine prior to the frozen timeout errors. And I was
> > using it in windows (same raid0 config) just fine with no errors what so
> > ever.
> 
> Can you post full dmesg output?  The above doesn't tell much about ATA
> side of things.
> 
> Thanks.
> 

Sure, I've attached the full dmesg from a full test I ran today (I couldn't 
find the old log where that bit came from). I'm running 2.6.31-rc9 right now, 
and will probably update to the final 31 release soonish. The test I ran 
actually finished (dd if=/dev/sdc of=/dev/null bs=8M), whereas with earlier 
kernels it was completely failing. Of course, I was actually trying to bring 
up the md raid0 array (2x2TB), mount the filesystem, and copy the files off 
before. mdraid is probably more sensitive to the end_request errors than dd 
is.

-- 
Thomas Fjellstrom
tfjellstrom@...w.ca

View attachment "disk.dmesg" of type "text/plain" (89011 bytes)