Hi there,
A couple days ago, I have converted my Ubuntu Precise machine from ext4
to BTRFS using btrfs-convert.
I currently use kernel:
Linux fnix 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
...and a btrfs-tools package more recent than the old one that came with
Ubuntu Precise:
Version: 0.19+20120328-4ubuntu1
After I had shifted, I tried to defragment and compress my FS using
commands such as :
find /mnt/STORAGEFS/STORAGE/ -exec btrfs fi defrag -clzo -v {} \;
During execution of such commands, my kernel oopsed, so I restarted.
Afterwards, I noticed that, during the execution of such a command, my
FS free space was quickly dropping, where I would have expected it to
increase...
Once finished, I checked a couple of BTRFS FSes using btrfsck, but I
interpret the results as having some errors :
root@fnix:/# btrfsck /dev/VG1/DEBMINT
checking extents
checking fs roots
root 256 inode 257 errors 800
found 7814565888 bytes used err is 1
total csum bytes: 6264636
total tree bytes: 394928128
total fs tree bytes: 365121536
btree space waste bytes: 101451531
file data blocks allocated: 20067590144
referenced 13270241280
Btrfs Btrfs v0.19
root@fnix:/# btrfsck /dev/VG1/STORAGE
checking extents
checking fs roots
root 301 inode 10644 errors 1000
root 301 inode 10687 errors 1000
root 301 inode 10688 errors 1000
root 301 inode 10749 errors 1000
found 55683117056 bytes used err is 1
total csum bytes: 54188580
total tree bytes: 191500288
total fs tree bytes: 103596032
btree space waste bytes: 49730472
file data blocks allocated: 55640522752
referenced 56466059264
Btrfs Btrfs v0.19
It doesn't seem that btrfsck attempts to fix these errors in any way...
It just displays them.
Besides this, my filesystem looks sane, but I suspect that at least my
"STORAGE" FS uses much more space than it should...
Are these errors serious ?Is there a way to get rid of them without
reformatting ?
TIA for any clue.
Best regards.
--
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
