This message means that the controller was sending a 6 bytes SCSI
command (PHASE 2 = COMMAND PHASE) but the device decided to switch to
STATUS PHASE (3) after having accepted 4 (6-2) bytes of the SCSI
command.
In such a situation the driver lets the device go to STATUS PHASE
as it shall.
In SCSI it is the targets that decide the phase sequence and not the
initiator. Obviously something did go wrong with either the device or
the actual data the device receives in command phase.
The minimal size for a SCSI command is 6 bytes. So, the device that has
only accepted 4 bytes should have reported an error condition, unless
it is bogus.
The low level drivers implement the SCSI transport protocol. They donnot,
normally act on SCSI statuses which are just reported to the upper
layer. Low-level drivers are aware of SCSI transport failures as
SCSI parity errors, Unexpected Disconnections, etc...
> also this may be related
>
> Aug 29 16:15:05 shawc kernel: EXT2-fs warning (device 08:13): ext2_free_inode: bit
> already cleared for inode 126597
It may.
But if the system did only report the 2 above error messages, that's not
normal at all, since:
- The device should have reported an error.
- The the scsi driver should have retried the command until succes or
an IO error should have been reported in your log.
So, it might be, in my opinion, that your system has some problem
elsewhere and that the SCSI problem you report may just be a consequence.
> Controller is an Asus PCI-SC860, disk is an IBM DDRS 34560.
I have a DDRS-34560W Firmware revision S71D connected on a 53C875 with
3 other Disks on the same SCSI BUS. I donnot have had problems with
this hard disk for the moment.
Regards,
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html