Re: btrfs: free space inode generation (0) did not match free space cache generation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 28.01.2011 14:45, Josef Bacik wrote:
It's not a problem, it just means that the cache is being discarded, which is
what is supposed to happen.  You probably ran out of space or one of the other
corner cases where we can't write out the space cache.  Thanks,

FYI, there is plenty of free space (~150 GB).

It could be some corner case:

- filesystem is mounted with compress-force,
- one kvm process (the only writer to btrfs) writes to the btrfs filesystem, via the virtual guest using a 220 GB qcow2 image file (lots of writes) and a 7 GB qcow2 image file (very few writes).


--
Tomasz Chmielewski
http://wpkg.org
--
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


[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux