I've just tested with the current daily kernel (after removing the /etc/modprobe.d/options I had added to set the max_speed parameter for the sbp2 module). The disk becomes read-only just as it does with the stock kernel. I forgot to mention that the disk has an ext4 filesystem on it.
This is the kernel I just tested: Linux mark-laptop 2.6.35-999-generic #201007071232 SMP Wed Jul 7 11:36:58 UTC 2010 x86_64 GNU/Linux Here is the output from syslog around the time the hard-drive becomes read-only: Jul 7 18:38:33 mark-laptop kernel: [ 1671.120056] ieee1394: sbp2: aborting sbp2 command Jul 7 18:38:33 mark-laptop kernel: [ 1671.120076] sd 6:0:0:0: [sdb] CDB: Write(10): 2a 00 00 e6 74 3f 00 04 00 00 Jul 7 18:38:43 mark-laptop kernel: [ 1681.120047] ieee1394: sbp2: aborting sbp2 command Jul 7 18:38:43 mark-laptop kernel: [ 1681.120067] sd 6:0:0:0: [sdb] CDB: Test Unit Ready: 00 00 00 00 00 00 Jul 7 18:38:43 mark-laptop kernel: [ 1681.120201] ieee1394: sbp2: reset requested Jul 7 18:38:43 mark-laptop kernel: [ 1681.120216] ieee1394: sbp2: generating sbp2 fetch agent reset Jul 7 18:38:53 mark-laptop kernel: [ 1691.120048] ieee1394: sbp2: aborting sbp2 command Jul 7 18:38:53 mark-laptop kernel: [ 1691.120069] sd 6:0:0:0: [sdb] CDB: Test Unit Ready: 00 00 00 00 00 00 Jul 7 18:38:53 mark-laptop kernel: [ 1691.120186] sd 6:0:0:0: Device offlined - not ready after error recovery Jul 7 18:38:53 mark-laptop kernel: [ 1691.120239] sd 6:0:0:0: [sdb] Unhandled error code Jul 7 18:38:53 mark-laptop kernel: [ 1691.120248] sd 6:0:0:0: [sdb] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK Jul 7 18:38:53 mark-laptop kernel: [ 1691.120261] sd 6:0:0:0: [sdb] CDB: Write(10): 2a 00 00 e6 74 3f 00 04 00 00 Jul 7 18:38:53 mark-laptop kernel: [ 1691.120292] end_request: I/O error, dev sdb, sector 15103039 Jul 7 18:38:53 mark-laptop kernel: [ 1691.120310] Buffer I/O error on device sdb1, logical block 1887872 Jul 7 18:38:53 mark-laptop kernel: [ 1691.120321] lost page write due to I/O error on sdb1 There are hundreds of error messages after this relating to I/O errors and read-only filesystems. Please let me know if the full syslog is useful. The error messages with the Lucid kernel (2.6.32-23-generic) look identical to me. I should point out that this disk mounts fine and I can read and write individual files to it with no problem--it seems to be backup programs that make it freeze up. ** Tags removed: needs-upstream-testing -- external firewire hard drive becomes read-only during backup https://bugs.launchpad.net/bugs/602452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
