On Thu, Aug 27, 2015 at 11:41 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Thu, Aug 27, 2015 at 11:33 AM, Mike Aubury <mike@xxxxxxxxx> wrote: >> # btrfs dev scan >> Scanning for Btrfs filesystems >> >> (back to # prompt) >> >> >> # mount -o ro,degraded /data >> >> >> Seems to work, /data is mounted >> >> # btrfs fi show >> Label: '0e36d290:data' uuid: e75a9856-d9e5-4d02-92e6-a217056c69b7 >> Total devices 4 FS bytes used 6.09TiB >> devid 1 size 2.71TiB used 2.71TiB path /dev/md127 >> devid 2 size 1.82TiB used 1.82TiB path /dev/md126 >> devid 3 size 1.82TiB used 1.82TiB path /dev/md125 >> *** Some devices missing >> >> >> Where next ? Well now at least you can suck the data off the volume... If you can't figure out why the loop back mount device continues to be missing, you might as well just take advantage of the fact you've got it ro mounted and get everything off the volume in preparation to wipe it and start over. -- Chris Murphy -- 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
