From owner-freebsd-fs@FreeBSD.ORG Thu Feb 21 19:07:12 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 55A00347; Thu, 21 Feb 2013 19:07:12 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by mx1.freebsd.org (Postfix) with ESMTP id B8FF4220; Thu, 21 Feb 2013 19:07:11 +0000 (UTC) Received: by mail-bk0-f53.google.com with SMTP id j10so4240626bkw.40 for ; Thu, 21 Feb 2013 11:07:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bEA4zuirgVUuOV99wU7y7zIaXL8UT8/6iXIjaQFp9Yk=; b=Bzeamx+Pl52jSjLjffP2m7YluD3Tx7vBrEX2PDU9grJtqpT3sofIAaQC3dVOsYqyPr 6wNudlyyA61KRlYUw3jJ1TytnVOTfuaSxs4G9MaLsts3aYcTNgIrcVOaz0ludoAL5bT/ yCyk5/2WSTPEB/1KzbkNBWJ+UAlAgL0cWWiQyTUbTQ2vRRwJ2fY95YLFfMrCH7aI389O AWU0MQc36Ktsaqwy2v9jjtQklJktKszrobSNsaMLv0vYmbziaI6yhvqT9m3/A/LmsOm+ aZJa/bhw28kod6Mqq8DdFLp86fQM9HGu67F6Wqlnn/ZfveYy53NgOVxla4O3sHwPzSfC TOlg== X-Received: by 10.204.8.16 with SMTP id f16mr11376400bkf.81.1361473625153; Thu, 21 Feb 2013 11:07:05 -0800 (PST) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id go8sm24841835bkc.20.2013.02.21.11.07.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Feb 2013 11:07:03 -0800 (PST) Sender: Alexander Motin Message-ID: <51267055.3040500@FreeBSD.org> Date: Thu, 21 Feb 2013 21:07:01 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130125 Thunderbird/17.0.2 MIME-Version: 1.0 To: Jeremy Chadwick Subject: Re: disk "flipped" - a known problem? References: <20130121221617.GA23909@icarus.home.lan> <50FED818.7070704@FreeBSD.org> <20130125083619.GA51096@icarus.home.lan> <20130125211232.GA3037@icarus.home.lan> <20130125212559.GA1772@icarus.home.lan> <20130125213209.GA1858@icarus.home.lan> <20130126011754.GA1806@icarus.home.lan> In-Reply-To: <20130126011754.GA1806@icarus.home.lan> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, avg@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 19:07:12 -0000 On 26.01.2013 03:17, Jeremy Chadwick wrote: > Okay, I've figured out the exact, 100% reproducible condition that > causes the situation. It took me a lot of tries and a digital pocket > recorder to take verbal notes (there are just too many things to look at > simultaneously), but I've figured it out. > > I'm sorry for the verbosity, but it's necessary. > > Assume the disk we're talking about is /dev/ada5. > > 1. Prior to any issues, we have this: > > root@icarus:~ # ls -l /dev/ada5* /dev/xpt* /dev/pass5* > crw-r----- 1 root operator 0x8c Jan 25 16:41 /dev/ada5 > crw------- 1 root operator 0x75 Jan 25 16:35 /dev/pass5 > crw------- 1 root operator 0x51 Jan 25 16:35 /dev/xpt0 > > 2. ada5 begins experiencing issues -- ATA commands (CDBs) submit do not > get a response (not going to discuss how/why that can happen). > > 3. These types of messages are seen on console (naturally the CDB and > request type will vary -- in this case it was because I was doing the dd > zero'ing, thus tickling the bad sector/naughty firmware on the drive): > > Jan 25 16:29:28 icarus kernel: ahcich5: Timeout on slot 0 port 0 > Jan 25 16:29:28 icarus kernel: ahcich5: is 00000000 cs 00000000 ss 00000001 rs 00000001 tfd 40 serr 00000000 cmd 0004c017 > Jan 25 16:29:28 icarus kernel: ahcich5: AHCI reset... > Jan 25 16:29:28 icarus kernel: ahcich5: SATA connect time=1000us status=00000113 > Jan 25 16:29:28 icarus kernel: ahcich5: AHCI reset: device found > Jan 25 16:29:28 icarus kernel: (ada5:ahcich5:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 80 80 77 01 40 00 00 00 00 00 00 > Jan 25 16:29:28 icarus kernel: (ada5:ahcich5:0:0:0): CAM status: Command timeout > Jan 25 16:29:28 icarus kernel: (ada5:ahcich5:0:0:0): Retrying command > > 4. Any I/O submit to ada5 during this time blocks (this is normal). > > 5. **While this situation is happening**, something using xpt(4) > attempts to submit a CDB to the disk (ex. smartctl -a /dev/ada5). > This request also blocks (again, normal). > > 6. Physical device falls off bus, or CAM kicks the disk off the bus. > Doesn't matter which. We see messages resembling this (boy am I tired > of this interspersed output problem): > > Jan 25 16:29:32 icarus kernel: (ada5:ahcich5:0:0:0): lost device > Jan 25 16:29:32 icarus kernel: (pass5:ahcich5:0:0:0): lost device > Jan 25 16:29:32 icarus kernel: (ada5:ahcich5:0:0:0): removing device entry > Jan 25 16:29:32 icarus kernel: (pass5:ahcich5:0:0:0): passdevgonecb: devfs entry is gone > > 7. Standard I/O requests fail with errno=6 "Device not configured". > xpt(4) requests also fail with the same errno. > > 8. Device-wise, at this stage all we have is: > > root@icarus:~ # ls -l /dev/ada5* /dev/xpt* /dev/pass5* > crw------- 1 root operator 0x51 Jan 25 16:35 /dev/xpt0 > > 9. Device comes back online for whatever reason. FreeBSD sees the disk, > blah blah blah: > > Jan 25 16:30:16 icarus kernel: GEOM: new disk ada5 > Jan 25 16:30:16 icarus kernel: ada5: ATA-7 SATA 1.x device > Jan 25 16:30:16 icarus kernel: ada5: Serial Number WD-WMAP41573589 > Jan 25 16:30:16 icarus kernel: ada5: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) > Jan 25 16:30:16 icarus kernel: ada5: Command Queueing enabled > Jan 25 16:30:16 icarus kernel: ada5: 143089MB (293046768 512 byte sectors: 16H 63S/T 16383C) > Jan 25 16:30:16 icarus kernel: ada5: Previously was known as ad14 > > ...um, where's pass5? > > 10. /dev/pass5 is now completely (permanently) missing: > > root@icarus:~ # ls -l /dev/ada5* /dev/xpt* /dev/pass5* > crw-r----- 1 root operator 0x99 Jan 25 16:42 /dev/ada5 > crw------- 1 root operator 0x51 Jan 25 16:35 /dev/xpt0 > > 11. Any further attempts to communicate via xpt(4) with ada5 fail. > Detaching and reattaching the disk does not fix the issue; the only fix > is to reboot the system. > > 12. "camcontrol debug -IPXp scbus5" results in tons and tons of output > all pertaining to xpt(4). It looks like xpt(4) is in some kind of > loop. > > Below is my verbose boot (with non-kernel things removed), which > also includes "camcontrol debug" output once things are in a bad state: > > http://jdc.koitsu.org/freebsd/xpt_oddity.log > > In this log you'll see that after 1 CAM timeout I yanked the drive, then > roughly 30 seconds later reinserted it. > > If you need me to turn on CAM debugging *prior* to the above, I can do > that, just let me know. > > The important step is #5. Without that, the problem shown in #9/10/11 > does not happen. > > It's a good thing I don't run smartd(8) -- most users I see using that > software set the interval to something like 180s or 60s. Imagine this > frustration: "okay so the disk fell off the bus, but what, now I can't > talk to it with SMART? Uhhh... Err, works now? Whatever". I think, the problem may already be fixed in HEAD by r244014 by ken@. I've just merged it to 9-STABLE at r247115. So if it is still possible to reproduce the situation, it would be good to try. -- Alexander Motin