>> If it is unknown, which of these options have been used at btrfs >> creation time - is it possible to check the state of these options >> afterwards on a mounted or unmounted filesystem? >> > I don't think there is a specific tool for doing this, but some of them > do show up in dmesg, for example skinny-metadata shows up as a mention > of the FS having skinny extents. > Devs, It may be helpful to include the device in the kernel log for skinny extents. Currently it shows up like the following which is a little ambiguous: [ 6.050134] BTRFS info (device sde3): disk space caching is enabled [ 6.056606] BTRFS: has skinny extents <snipped> [ 7.740986] BTRFS info (device sde3): enabling auto defrag [ 7.747151] BTRFS info (device sde3): disk space caching is enabled <snipped> [ 7.908906] BTRFS info (device sde2): enabling auto defrag [ 7.915031] BTRFS info (device sde2): disk space caching is enabled [ 8.071033] BTRFS info (device sde4): enabling auto defrag [ 8.076715] BTRFS info (device sde4): disk space caching is enabled [ 8.082187] BTRFS: has skinny extents [ 8.513502] BTRFS info (device sde5): enabling auto defrag [ 8.518887] BTRFS info (device sde5): disk space caching is enabled [ 8.524064] BTRFS: has skinny extents [ 9.634285] BTRFS info (device sdd6): enabling auto defrag [ 9.639308] BTRFS info (device sdd6): disk space caching is enabled [ 9.644338] BTRFS: has skinny extents Thanks, Kyle -- 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
