Thanks for looking, let me know if you need any other info. I haven't touched the system yet, but it appears I'll need to unmount to btrfs check or mount rw,recovery to try and get it working again. Who knows what will happen then? I can leave it as if for a few days if it will help any diagnosis. Thanks again. On Wed, Aug 19, 2015 at 11:17 PM, Anand Jain <anand.jain@xxxxxxxxxx> wrote: > > two to dig more.. > >> Aug 16 04:41:31 [1082957.226817] BTRFS: error (device sdb) in >> __btrfs_free_extent:6235: errno=-28 No space left >> Aug 16 04:41:31 [1082957.226819] BTRFS info (device sdb): forced readonly > > > :: > >> Aug 16 04:41:31 [1082957.289289] BTRFS: error (device sdb) in >> cleanup_transaction:1692: errno=-5 IO failure > > > 1. > We probably need to understand what kicked in readonly. is it > -28 (No space left) OR -5 (EIO). > > 2. > There are no media errors from the block layer, hope we are not > fabricating the EIO in the FS layer... thats wrong. > > digging more. > > Thanks, Anand -- 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
