From: Chris Mason <chris.mason@oracle.com>
To: "Nathan A. Mourey II" <nmoureyii@ne.rr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-fsdevel@vger.kernel.org
Subject: Re: Kernel bug with btrfs on laptop with external hd and suspend and resume.
Date: Fri, 17 Feb 2012 08:34:56 -0500 [thread overview]
Message-ID: <20120217133456.GG21896@shiny> (raw)
In-Reply-To: <1329428930.6062.4.camel@firefly>
On Thu, Feb 16, 2012 at 04:48:50PM -0500, Nathan A. Mourey II wrote:
> I booted up my laptop with my eSATA drives attached and mounted. I then
> closed the lid without logging in. It then when to sleep mode. I was
> wrong in my first post about the computer suspending. It didn't suspend
> to disk, as I would have noticed the hd light. The drives where not
> unplugged at any time. It looks like the problem occurred when trying
> to stop the disks. I was able to do a hard reboot and the disk came up
> fine. Once again I hope that this helps.
>
>
> Feb 14 14:46:39 firefly kernel: [ 96.374559] Restarting tasks ...
> Feb 14 14:46:39 firefly kernel: [ 96.375986] XFS (sdb1): xfs_do_force_shutdown(0x1) called from line 1033 of file fs/xfs/xfs_buf.c. Return address = 0xffffffffa05f18ba
> Feb 14 14:46:39 firefly kernel: [ 96.375993] XFS (sdb1): I/O Error Detected. Shutting down filesystem
> Feb 14 14:46:39 firefly kernel: [ 96.376017] XFS (sdb1): Please umount the filesystem and rectify the problem(s)
> Feb 14 14:46:39 firefly kernel: [ 96.384244] sd 4:0:0:0: [sdb] Synchronizing SCSI cache
> Feb 14 14:46:39 firefly kernel: [ 96.384280] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> Feb 14 14:46:39 firefly kernel: [ 96.384284] sd 4:0:0:0: [sdb] Stopping disk
> Feb 14 14:46:39 firefly kernel: [ 96.384291] sd 4:0:0:0: [sdb] START_STOP FAILED
> Feb 14 14:46:39 firefly kernel: [ 96.384293] sd 4:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
These messages look like the drive wasn't up and running when the
filesystem tried to talk with it. Both XFS and btrfs are having trouble
(some more gracefully than others) so this should be a problem in the
resume code.
-chris
prev parent reply other threads:[~2012-02-17 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328990690.2464.6.camel@firefly>
2012-02-13 14:17 ` Kernel bug with btrfs on laptop with external hd and suspend and resume Srivatsa S. Bhat
2012-02-13 14:41 ` Chris Mason
2012-02-16 21:48 ` Nathan A. Mourey II
2012-02-17 13:34 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120217133456.GG21896@shiny \
--to=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nmoureyii@ne.rr.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).