From: "Martin K. Petersen" <mkp@mkp.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
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: Fri, 17 Aug 2007 08:36:33 -0400 [thread overview]
Message-ID: <yq1ps1m5odq.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <46C3EE1F.40309@s5r6.in-berlin.de> (Stefan Richter's message of "Thu, 16 Aug 2007 08:26:39 +0200")
>>>>> "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.
--
Martin K. Petersen http://mkp.net/
next prev parent reply other threads:[~2007-08-17 12:36 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 [this message]
2007-08-18 13:27 ` Stefan Richter
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=yq1ps1m5odq.fsf@sermon.lab.mkp.net \
--to=mkp@mkp.net \
--cc=gjasny@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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®