Since nobody had any other suggestions, I decided to attempt to run
modified btrfsck with --repair option (without BUG_ON(rec-is_root)
assertion).
Surprisingly modified btrfsck --repair fixed all errors but one
(according to btrfsck), but btrfsck asked me to run btrfsck --repair one
On 2014-11-24 02:46, Duncan wrote
if you were using gmane's web service, that explains things as
weaverd, the process
that does the threading on the web side, was down for some days
Yes, I have used gmane blog. Good to know it is not down anymore.
Back on topic. Even after updating
In attempt to get more information, I have commented out
BUG_ON(rec-is_root) in cmds-check.c to let btrfsck check my file system
without failing on this assertion. Below you can see the output. I would
appreciate any help or ideas...
# btrfsck /dev/sdb1 # Full log can be downloaded
I suggest upgrading and just posting the results from 'btrfs check
device'
without any options and see what you get.
OK, I have upgraded to 3.17.0 kernel and I also have upgraded
btrfs-tools:
# btrfs --version
Btrfs v3.17
# btrfs check /dev/sdb1
Checking filesystem on /dev/sdb1
UUID:
On 2014-11-21 04:35, Roman Mamedov wrote:
On Fri, 21 Nov 2014 01:27:17 +
Boris Chernov aqs1...@hotmail.com wrote:
I have changed file system label few times in total. When I tried
to mount it after that, it became not mountable:
# mount /dev/sdb1 /mnt
mount: Not a directory
I'd say
I have changed file system label few times in total. When I tried
to mount it after that, it became not mountable:
# mount /dev/sdb1 /mnt
mount: Not a directory
In dmesg I see the following after above command:
[ 5198.413202] BTRFS info (device sdb1): disk space caching is enabled
[
