On lör, 2013-06-29 at 03:08 -0600, cwillu wrote:
Not sure I entirely follow: mounting with -o degraded (not -o
recovery) is how you're supposed to mount if there's a disk missing.
What I'm wondering about is why btrfsck segfaults, why it won't claim
which drive is supposedly corrupt in a
Hi,
I'm evaluating btrfs for a future deployment, and managed to
(repeatedly
) get btrfs to the state where the system can't mount, can't fsck and
can't
recover.
The test setup is pretty small, 6 devices of various size:
butter-1.5GA vg_dolt -wi-a
1.50g
butter-1.5GB vg_dolt
Making this with all 6 devices from the beginning and btrfsck doesn't
segfault. But it also doesn't repair the system enough to make it
mountable. ( nether does -o recover, however -o degraded works, and
files
are then accessible )
Not sure I entirely follow: mounting with -o degraded (not
