On Tue, Aug 11, 2015 at 12:04 PM, Timothy Normand Miller <theo...@gmail.com> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=102691 [ 7.729124] BTRFS: device fsid ecdff84d-b4a2-4286-a1c1-cd7e5396901c devid 2 transid 226237 /dev/sdd [ 7.746115] BTRFS: device fsid ecdff84d-b4a2-4286-a1c1-cd7e5396901c devid 4 transid 226237 /dev/sdb [ 7.826493] BTRFS: device fsid ecdff84d-b4a2-4286-a1c1-cd7e5396901c devid 3 transid 226237 /dev/sdc What do you get for 'btrfs fi show' I see devid 2, 3, 4 only for this volume UUID. So you definitely appear to have a failed device and that's why it doesn't mount automatically at boot time. You just need to use -o degraded, and that should work assuming no problems with the other three devices. If it does work, 'btrfs replace start...' is the ideal way to replace the failed drive. Maybe someone else can say whether nodatacow as a subvolume mount option will apply this to the entire volume. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
