Hi, I have a btrfs volume that I can't mount RW (but I can mount and use it RO). So, at boot time, the partition is mounted RO (defaults,noatime,compress-force=zlib,nossd,ro) : Feb 1 22:30:12 frozen kernel: [ 8.646350] Btrfs loaded Feb 1 22:30:12 frozen kernel: [ 8.650878] device fsid cf2c98bd-147b-400e-bca5-79765650b1a7 devid 1 transid 376249 /dev/mapper/vg--frozen-backup Feb 1 22:30:12 frozen kernel: [ 8.652740] btrfs: force zlib compression Feb 1 22:30:12 frozen kernel: [ 8.652750] btrfs: not using ssd allocation scheme Feb 1 22:30:12 frozen kernel: [ 8.652756] btrfs: disk space caching is enabled then I do : mount -o rw,remount /backup/ Feb 1 22:32:38 frozen kernel: [ 65.780686] btrfs: force zlib compression Feb 1 22:32:38 frozen kernel: [ 65.780700] btrfs: not using ssd allocation scheme Feb 1 22:32:38 frozen kernel: [ 65.780706] btrfs: disk space caching is enabled I let that mount run days, without any success. It stay running, and I can't interrupt it (CTRL+C or kill). There is nothing about btrfs in kern.log, and when I run btrfsck it throw OOM because it use the 10GB of RAM of the system. It's a 2TB volume, running a 3.7.1 kernel : # btrfs fi df /backup/ Data: total=1.72TB, used=1.65TB System, DUP: total=64.00MB, used=208.00KB System: total=4.00MB, used=0.00 Metadata, DUP: total=39.20GB, used=35.38GB If it's a btrfs bug, can I give you any information to help fix that ? Thanks, Olivier -- 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
