I get a lot “aborting sbp2 command” lines in syslog, followed by I/O errors. Why, and what can I do about it?
Possible causes are bugs in Linux, firmware bugs of the drive, or defective hardware. Make sure the drive and bridge do not overheat, which happens easily in non-ventilated enclosures. Look for a firmware update: Firmware Downloads. Alas, firmware updaters typically run on Windows or Mac OS, and some SBP-2 bridges cannot be updated at all. Use serialized sbp2 operation (see parameters on sbp2 driver page). Note, serialized I/O is already the default mode since Linux 2.6.14, i.e. you don’t need special load parameters. (You can check that you have the correct parameters: “cat /sys/module/sbp2/parameters/serialize_io” should show 1 or Y.) By the way, you should use much more recent kernels than 2.6.14 anyway if you want reliable SBP-2. Post-2.6.22 kernels need to use the workarounds=1 option to firewire_sbp2. This claim is just wrong. The flag 1 is no fix for this. Under Linux 2.6, try the CFQ I/O scheduler: echo cfq > /sys/block/sda/queue/scheduler (Replace sda by the correct device nam
