I observe that whenever I create a BtrFS instance using mkfs.btrfs, there is always the leftover cruft of two System/Metadata-Single allocation profiles:
btrfs fi df /run/media/samjnaa/BRIHATII/ Data, single: total=460.01GiB, used=458.47GiB System, DUP: total=8.00MiB, used=80.00KiB System, single: total=4.00MiB, used=0.00B Metadata, DUP: total=1.50GiB, used=736.86MiB Metadata, single: total=8.00MiB, used=0.00B GlobalReserve, single: total=256.00MiB, used=0.00B Doing btrfs balance eventually removes these (but since I forgot to do it *before* copying 400+ G of data to the drive it's still running) but I don't understand why these have to be created in the first place? (I just used SuSE Tumbleweed's default mkfs.btrfs without any -m or -d options.) -- Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा -- 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
