On Mon, Aug 10, 2015 at 7:23 PM, Timothy Normand Miller <theo...@gmail.com> wrote: > On Mon, Aug 10, 2015 at 6:52 PM, Chris Murphy <li...@colorremedies.com> wrote:
>> - complete dmesg for the failed mount > > It really doesn't say much. I have things like this: > [ 8.643535] BTRFS info (device sdc): disk space caching is enabled > [ 8.643789] BTRFS: failed to read the system array on sdc > [ 8.706062] BTRFS: open_ctree failed > [ 8.707124] BTRFS info (device sdc): disk space caching is enabled > [ 8.710924] BTRFS: failed to read the system array on sdc > [ 8.766080] BTRFS: open_ctree failed > [ 8.766903] BTRFS info (device sdc): setting nodatacow, compression > disabled > [ 8.766905] BTRFS info (device sdc): disk space caching is enabled > [ 8.767152] BTRFS: failed to read the system array on sdc > [ 8.936019] BTRFS: open_ctree failed > [ 8.936906] BTRFS info (device sdc): disk space caching is enabled > [ 8.939922] BTRFS: failed to read the system array on sdc > [ 8.995984] BTRFS: open_ctree failed > [ 8.996796] BTRFS info (device sdc): disk space caching is enabled > [ 8.997093] BTRFS: failed to read the system array on sdc > [ 9.125936] BTRFS: open_ctree failed It looks like there's not enough redundancy remaining to mount and in such a case there's really not much to be done. I don't see nodatacow in your fstab, so I don't know why that's happening. That means no checksumming for data. > > Also, when I manually try to mount, I get things like this: > > # mount /mnt/btrfs > mount: wrong fs type, bad option, bad superblock on /dev/sdc, > missing codepage or helper program, or other error Have you tried to mount with -o degraded? > Well, if I get something lengthy, I'll attach it to my bug report. > Did the information I reported help at all? The entire dmesg is still useful because it should show libata errors if these aren't fully failed drives. So you should file a bug and include, literally, the entire unedited dmesg. -- 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
