Hi, Can not delete data from btrfs volume after move from 3.8 kernel to 3.12 I've upgraded kernel on one of the x86-64 servers from 3.8.10 to 3.12 (both vanilla). This was single volume encrypted via dev mapper (luks). After upgrade mounting the volume did not work (failed on UUID tree creation ?) Nov 5 00:01:39 eire kernel: btrfs: device label dat devid 1 transid 195666 /dev/mapper/dat Nov 5 00:01:39 eire kernel: btrfs: disabling disk space caching Nov 5 00:01:39 eire kernel: btrfs: force clearing of disk cache Nov 5 00:01:39 eire kernel: btrfs: setting nodatacow, compression disabled Nov 5 00:01:39 eire kernel: btrfs: disabling tree log Nov 5 00:01:39 eire kernel: btrfs: enabling auto recovery Nov 5 00:01:40 eire kernel: btrfs: creating UUID tree Nov 5 00:01:44 eire kernel: btrfs: failed to create the UUID tree -28 (in above attempt I tried to disable cow, clear cache, disable space cache but same problem was reported while using default mount options) I've reverted to 3.8.10 kernel where it was possible to mount the filesystem but I was no longer able to delete or create any files off it. I tried clobbering the file as suggested on wiki pages, mounting with recovery options,running btrfs-zero-log, nothing worked. btrfs-image attached.
btrfs-image is available for download here: http://www.kulicki.com/btrfs_broken.image
The error returned while removing files was "No space left on device"
Just to keep the bugzilla up to date, this was sent on the mailing list (note the 98%): Hi Stefan, Yes, I realise that. As I pointed out in bug report I have tried workarounds suggested in wiki and more. To be precise: partial balancing didn't work (completed without error but no change), balacing fs failed with ENOSPC, clobbering a file didn't work (ENOSPC), btrfs-zero-log completed but no change. The filesystem was quite full 98% but I could still write to it before rebooting with new kernel. I had to nuke the fs since then and restore from backup but I captured image with btrfs-image before running btrfs-zero-log. regards, Bart On Thu, Nov 7, 2013 at 8:49 AM, Stefan Behrens <sbehrens@giantdisaster.de> wrote: > On Wed, 6 Nov 2013 21:53:25 +0000, Bartosz Kulicki wrote: >> As per subject. Seems UUID tree creation failed after upgrade. I could >> not mount filesystem under 3.12. Going back to 3.8.10 allowed me to >> mount fs but I could no longer perform any deletes, writes etc. >> >> I've opened a bug report here. >> https://bugzilla.kernel.org/show_bug.cgi?id=64461 >> >> I've included link to image captured with btrfs-image. >> >> Please CC me if further information is needed as I'm not subscribed to >> the mailing list. >> > > ENOSPC means you're out of disk space. A copy-on-write filesystem needs > disk space for delete operations, that's not a bug. > > What does 'btrfs fi df /mountpoint' say? > How much disk space do you have, how much is allocated? > > And try the procedure that is described in the wiki: > > > https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_on_device.22_errors.2C_but_df_says_I.27ve_got_lots_of_space > > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html