Hey. I'm creating a filesystem on Samsung Evo 850 Pro on top of a dm- crypt/LUKS container (with TRIM not being passed on, for the usual security reasons): # mkfs.btrfs --label system /dev/mapper/system btrfs-progs v4.2.2 See http://btrfs.wiki.kernel.org for more information.
Label: system UUID: 65531196-2e43-4c49-b495-ac9abc57d7d8 Node size: 16384 Sector size: 4096 Filesystem size: 937.00GiB Block group profiles: Data: single 8.00MiB Metadata: DUP 1.01GiB System: DUP 12.00MiB SSD detected: no Incompat features: extref, skinny-metadata Number of devices: 1 Devices: ID SIZE PATH 1 937.00GiB /dev/mapper/system As you can see it doesn't detect the SSD. Isn't that kinda problematic cause btrfs does more when it detects and SSD than just using TRIM (e.g. not DUPing meta-data)? Can I somehow override this to get the SSD "detected"? Or what is the general suggestion here? Having it handled as SSD or as non-SSD, as said, when dm-crypt is used below and TRIM is not intended to be used. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
