Chris Murphy posted on Sun, 03 Jan 2016 14:33:40 -0700 as excerpted: > kernel-4.4.0-0.rc6.git0.1.fc24.x86_64 btrfs-progs 4.3.1 > > There was some copy pasting, hence /mnt/brick vs /mnt/brick2 confusion, > but the volume was always cleanly mounted and umounted. > > The biggest problem I have with all of this is the completely silent > addition of single chunks. That made the volume, in effect, no longer > completely raid1. No other details matter, except to try and reproduce > the problem, and find its source so it can be fixed. It is a bug, > because it's definitely not sane or expected behavior at all.
If there's no way you mounted it degraded,rw at any point, I agree, single mode chunks are unexpected on a raid1 for both data and metadata, and it's a bug -- possibly actually related to that new code that allows degraded,rw recovery via per-chunk checks. If however you mounted it degraded,rw at some point, then I'd say the bug is in wetware, as in that case, based on my understanding, it's working as intended. I was inclined to believe that was what happened based on the obviously partial sequence in the earlier post, but if you say you didn't... then it's all down to duplication and finding why it's suddenly reverting to single mode on non-degraded mounts, which indeed /is/ a bug. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- 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
