Messages in this thread | | | Date | Sat, 18 Aug 2007 15:27:35 +0200 | From | Stefan Richter <> | Subject | Re: Corrupted filesystem with new Firewire stack |
| |
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/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |