On Mon, 31 Mar 2014 19:45:27 +0000 (UTC), Duncan wrote:
> Hopefully, none of those commands included btrfsck --repair
... Woops...
Fortunately, it doesn't seem to have changed anything.
> That goes double if you're running raid5/6 mode
For the record, I've essentially just put Btrfs on 1 block device
with no special RAID structuring (I suppose that would be, in
your parlance, `single mode').
For completeness, this is the actual structure:
Raw disk
|
+-> MSDOS partition
|
+-> LVM2 logical volume
|
+-> LUKS dm-crypt device
|
+-> Btrfs
I apologize if that ASCII art fails to render properly on your end.
> I'd actually put more faith in the btrfs balance command...
> Btrfs scrub is another alternative
I suppose, then, that my ultimate plan of action is thus:
* Back up important data.
* Give `btrfs scrub' a try.
* Give `btrfs balance' a try.
* Rebuild the file system if necessary.
> or if you're running a mixed-data/metadata chunk filesystem, the
> default for filesystems under a gig, which further defaults to
> dup mode if on a single device
Just as an aside, I find it odd that the default for such a small
system would be to duplicate user data.
--------
Thanks for your insights!
--
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
