-----BEGIN PGP SIGNED MESSAGE-----
On Friday, 2013-07-12 at 17:29 +0200, David Sterba wrote:
On Wed, Jul 03, 2013 at 07:39:54PM +0200, Carlos E. R.
One of the
things that is a roadblock for many is the lack of repair tools.
Meaning a complete fsck.btrfs module.
If it's not complete, what's missing? I know about a few things that
could be added to extend fsck/repair coverage but I'm curious about your
I looked at it some time ago, and it was simply a script to fool the boot
process, it did absolutelly nothing. Now it is a binary, but I do not know
what it does - look:
cer@Telcontar:~> man fsck.btrfs
No manual entry for fsck.btrfs
btrfsck is part of btrfs-progs. Btrfs is currently under
heavy development, and not suitable for any uses other
than benchmarking and review. Please refer to the btrfs
for further details.
So, if the manual says it is not ready... do you really expect us to use it? ;-)
eleanor3:~ # btrfsck --help
btrfsck: unrecognized option '--help'
usage: btrfsck dev
It does run, though:
eleanor3:~ # btrfsck /dev/sda9
checking fs roots
checking root refs
found 300769280 bytes used err is 0
total csum bytes: 291300
total tree bytes: 2281472
total fs tree bytes: 1662976
btree space waste bytes: 448961
file data blocks allocated: 298487808
I do remember several posts of people using btrfs, got a broken
filesystem, could do nothing to repair it but reformat and recover from
backup, if it existed. Almost all of them said they were reformatting as
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org