On Wed, May 4, 2016 at 5:21 PM, Niccolò Belli <darkba...@linuxsystems.it> wrote:
> rw,noatime,compress=lzo,ssd,discard,space_cache,autodefrag,subvolid=257,subvol=/@ I suggest using defaults for starters. The only thing in that list that needs be there is either subvolid or subvold, not both. Add in the non-default options once you've proven the defaults are working, and add them one at a time. > I have the whole rootfs encrypted, including boot. I followed these steps: > https://wiki.archlinux.org/index.php/Dm-crypt/Encrypting_an_entire_system#Btrfs_subvolumes_with_swap > > Disk is a SAMSUNG SSD PM851 M.2 2280 256GB (Firmware Version: EXT25D0Q). The firmware is old if I understand the naming scheme used by Dell. It says EXT49D0Q is current. http://www.dell.com/support/home/al/en/aldhs1/Drivers/DriversDetails?driverId=0NXHH If you need to update, you may be best off doing a whole device trim, which is easiest done with mkfs.btrfs pointed at the whole device. I wouldn't trust any data on the drive after a firmware update so I'd start over entirely from scratch, new partition map, new everything. So the way to do this is: mkfs.btrfs /dev/sda wipefs -a /dev/sda That way the btrfs magic is removed, and now you can partition it, setup dmcrypt, etc. I advice using all defaults for everything for now, otherwise it's anyone's guess what you're running into. Off topic, but at least gmail users see your posts go to spam because your domain is configured to disallow relaying. Most mail services ignore this request by the domain but google honors it so no amount of training will make your email not spam. This is what's in your emails that's causing the problem: dmarc=fail (p=QUARANTINE dis=NONE) header.from=linuxsystems.it http://webmasters.stackexchange.com/questions/76765/sent-emails-pass-spf-and-dkim-but-fail-dmarc-when-received-by-gmail http://www.pcworld.com/article/2141120/yahoo-email-antispoofing-policy-breaks-mailing-lists.html -- Chris Murphy -- 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
