On 10/03/12 16:44, Bruno Friedmann wrote:
I've saw exactly the same situation in a vm / being full 360Mb free during a zypper dup
Was hardtime to understand
yeah, lost quite a bit of hair trying to figure it out :-S what's happening until I catch snapper eating 9.8Go of the 16Gb
(I think a ratio of a maximum of 50% should be never exceeded for snapshots)
Then I user snapper delete to remove any snapshot referenced in the .snapshot
After that I use rm -fr .snapshots and even the read-only message I was able to recover a lot of place.
All actions were a bit vodoo so can't be really reported as a nice bug. Just say take care of snapper, .snapshot : it seems that the default used are not suitable.
In this case the kernel BUGS in btrfs_unlink_subvol() exactly in http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=fs/btr... line 2951 btrfs_i_size_write(dir, dir->i_size - name_len * 2); dir->i_mtime = dir->i_ctime = CURRENT_TIME; ret = btrfs_update_inode(trans, root, dir); BUG_ON(ret); --> bang, here we go... btrfs_free_path(path); return 0; and my efforts to delete anything are futile :-( -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org