linux-kernel - Re: Corrupted filesystem with new Firewire stack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Aug 2007 08:36:33 -0400
From:	"Martin K. Petersen" <mkp@....net>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Gregor Jasny <gjasny@...glemail.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: Corrupted filesystem with new Firewire stack

>>>>> "Stefan" == Stefan Richter <stefanr@...6.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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/