Am Sat, 19 Jul 2014 19:11:00 -0600 schrieb Chris Murphy <li...@colorremedies.com>:
> I'm seeing this also in the 2nd dmesg: > > [ 249.893310] BTRFS error (device sdg2): free space inode generation (0) did > not match free space cache generation (26286) > > > So you could try umounting the volume. And doing a one time mount with the > clear_cache mount option. Give it some time to rebuild the space cache. > > After that you could umount again, and mount with enospc_debug and try to > reproduce the enospc with another balance and see if dmesg contains more > information this time. OK, I did that, and the new dmesg is attached. Also, some outputs again, first "filesystem df" (that "total" surge at the end sure is consistent): # btrfs filesystem df /mnt Data, single: total=237.00GiB, used=229.67GiB System, DUP: total=32.00MiB, used=36.00KiB Metadata, DUP: total=4.50GiB, used=3.49GiB unknown, single: total=512.00MiB, used=0.00 And here what I described in my initial post, the output of "balance status" immediately after the error (turns out my memory was correct): btrfs filesystem balance status /mnt Balance on '/mnt' is running 0 out of about 0 chunks balanced (0 considered), -nan% left (Also, this is with Gentoo kernel 3.15.6 now.) -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
dmesg4.log.xz
Description: application/xz
signature.asc
Description: PGP signature
