On 2013/04/03 22:05, Chris Mason wrote:
Quoting Tsutomu Itoh (2013-04-02 21:19:06)
Hi,
When inode_cache was specified for the mount option, I encountered the
following messages at umount.
Step to reproduce:
mkfs.btrfs -f /dev/sdc4
mount -o compress=lzo,autodefrag,inode_cache /dev/sdc4 /test1
dd if=/dev/zero of=/test1/file1 bs=1M count=8192
dd if=/test1/file1 of=/dev/null bs=1M
rm -f /test1/file1
umount /test1
Apr 3 09:43:12 luna kernel: [ 554.639149] BTRFS error (device sdc4) in
btrfs_save_ino_cache:471: error 28
We're running out of space while saving the inode cache. Strictly
speaking this should not abort the FS. I'll take a look.
Umm, 8GB was only written in the filesystem of 20GB...
When only inode_cache was specified for the mount option
('mount -o inode_cache /dev/sdc4 /test1'), the error message was not output.
Is this information useful for any investigations?
Thanks,
Tsutomu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
