From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Martin K. Petersen" <mkp@mkp.net>
Cc: Gregor Jasny <gjasny@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux1394-devel@lists.sourceforge.net
Subject: Re: Corrupted filesystem with new Firewire stack
Date: Sat, 18 Aug 2007 15:27:35 +0200 [thread overview]
Message-ID: <46C6F3C7.3070002@s5r6.in-berlin.de> (raw)
In-Reply-To: <yq1ps1m5odq.fsf@sermon.lab.mkp.net>
Martin K. Petersen wrote:
>>>>>> "Stefan" == Stefan Richter <stefanr@s5r6.in-berlin.de> writes:
>
> Stefan> There were some similar reports involving that "status write
> Stefan> for unknown orb". I haven't found a way to reproduce it; I
> Stefan> noticed it only once in the logs here so far.
>
> I get those all the time. Just do heavy ext3 I/O to the drive.
>
> Happens here on both a G4 and an intel Mini. Both running FC7.
>
> Aug 17 08:24:08 mini kernel: firewire_sbp2: status write for unknown orb
> Aug 17 08:25:08 mini kernel: firewire_sbp2: sbp2_scsi_abort
> Aug 17 08:26:36 mini kernel: firewire_sbp2: status write for unknown orb
> Aug 17 08:27:36 mini kernel: firewire_sbp2: sbp2_scsi_abort
> Aug 17 08:33:51 mini kernel: firewire_sbp2: status write for unknown orb
> Aug 17 08:34:51 mini kernel: firewire_sbp2: sbp2_scsi_abort
>
> Lacie drive in both cases.
I replaced a HDD in my OFXW911 enclosure and am starting tests now.
While backing ~80 GB from its current reiserfs partition up in order to
reformat to ext3, using find | cpio, I got that error 4 times:
Aug 18 13:24:58 stein ReiserFS: sdd1: Using r5 hash to sort names
Aug 18 13:47:41 stein firewire_sbp2: status write for unknown orb
Aug 18 13:48:11 stein firewire_sbp2: sbp2_scsi_abort
Aug 18 14:18:30 stein firewire_sbp2: status write for unknown orb
Aug 18 14:19:00 stein firewire_sbp2: sbp2_scsi_abort
Aug 18 14:50:08 stein firewire_sbp2: status write for unknown orb
Aug 18 14:50:39 stein firewire_sbp2: sbp2_scsi_abort
Aug 18 14:57:24 stein firewire_sbp2: status write for unknown orb
Aug 18 14:57:54 stein firewire_sbp2: sbp2_scsi_abort
cpio finished with exit code 0, and I compared one of the directories
within which a command was aborted after remounting the disk. Seems
that error was properly recovered from.
I will test if more of these errors occur in write access or with ext3,
but at least I have a way now to get one error per ~20 minutes
continuous IO, on average. Then I will proceed to examine the new
stack's sources for potential related bugs. Will take a while though
because I have other projects going on at the moment.
--
Stefan Richter
-=====-=-=== =--- =--=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-08-18 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 21:47 Gregor Jasny
2007-08-16 6:26 ` Stefan Richter
2007-08-17 12:36 ` Martin K. Petersen
2007-08-18 13:27 ` Stefan Richter [this message]
2007-08-25 16:43 ` Stefan Richter
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=46C6F3C7.3070002@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=gjasny@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mkp@mkp.net \
/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
all inboxes | Powered by JetHome®