On Tue, Aug 11, 2015 at 3:57 PM, Chris Murphy <li...@colorremedies.com> wrote: > 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'
# btrfs fi show Label: none uuid: 49ac9ad2-b529-4e6e-aef9-1c5b9e8a72f8 Total devices 1 FS bytes used 28.33GiB devid 1 size 79.69GiB used 41.03GiB path /dev/sda3 Label: none uuid: ecdff84d-b4a2-4286-a1c1-cd7e5396901c Total devices 4 FS bytes used 1.46TiB devid 2 size 931.51GiB used 767.00GiB path /dev/sdd devid 3 size 931.51GiB used 760.03GiB path /dev/sdc devid 4 size 931.51GiB used 767.00GiB path /dev/sdb *** Some devices missing Label: none uuid: f9331766-e50a-43d5-98dc-fabf5c68321d Total devices 1 FS bytes used 2.99TiB devid 1 size 3.64TiB used 3.01TiB path /dev/sde1 btrfs-progs v4.1.2 > > 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. It's missing because I physically disconnected it. Someone on IRC suggested I try this in case the drive with the bad sector was interfering. Of course, now that I've done this and mounted read/write, we can't reintegrate the failing drive. If I lose the array, I won't cry. The backup appears to be complete. But it would be convenient to avoid having to restore from scratch, and I'm hoping this might help you guys too in some way. I really like btrfs, and I would like provide you with whatever info might contribute something. > > Maybe someone else can say whether nodatacow as a subvolume mount > option will apply this to the entire volume. At the moment, I'm only trying to mount the whole volume, just so I could recover and scrub it, although as I mentioned in my earlier email, the scrub aborts with no report of why and with "0 errors." -- Timothy Normand Miller, PhD Assistant Professor of Computer Science, Binghamton University http://www.cs.binghamton.edu/~millerti/ Open Graphics Project -- 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
