On 3/13/13 12:07 AM, Jérôme Poulin wrote: > On Tue, Mar 12, 2013 at 10:03 PM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote: >> [ 37.176790] BTRFS error (device dm-0) in __btrfs_free_extent:5143: IO failure >> [ 37.176791] btrfs is forced readonly >> [ 37.176793] btrfs: run_one_delayed_ref returned -5 >> > > > It seems the SSD has bad blocks now, BTRFS seems to abuse SSD disks, I > burnt 1 SSD disk and 2 USB flash drive since I'm using BTRFS, in about > 2 months for each. ddrescue'ing the SSD would probably give better > chances of recovery and give BTRFS/btrfsck a chance to write correctly > to the newly copied image. On what do you base that theory? I suppose it could be, but nothing in the logs necessarily suggests that. The "IO failure" is because the fs shut down, went readonly, and subsequent IOs got -EIO, I think. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
