On Fri, Mar 18, 2016 at 5:31 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Mar 18, 2016 at 12:02 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote: >> The main thing you haven't tried here is mount -o degraded, which >> is the thing to do if you have a missing device in your array. >> >> Also, that kernel's not really all that good for a parity RAID >> array -- it's the very first one that had the scrub and replace >> implementation, so it's rather less stable with parity RAID than the >> later 4.x kernels. That's probably not the issue here, though. > > > It's a 4.5.0 kernel with 3.19 progs. I'd update the progs even though And actually I'm wrong because it's possible progs 4.4.1 might help fix things. But really the problem is that -o degraded isn't work for the volume with a single missing device and I can't tell you why. It might be a bug, but it might be that progs 3.19 --repair wasn't a good idea to do on a volume with one missing device. I'm really skeptical of any sorts of repairs being allowed without a scary warning and requiring a force flag on volumes that are degraded. I know this is possible with ext4 and XFS, but that's only because they have no idea when the underlying raid is degraded. -- 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
