See also NVMe and DiskFailure.

Solid-state disks have low-level block fragmentation problems (see Anandtech article), and these problems will persist even after formatting. Most disk's block mapping table can be reset by issuing an ATA secure erase command.

Disable entropy collection from disk I/O

With rotating disks, the amount of time to write a block is used as source of entropy. With SSDs, the time is so fast that it no longer is a good entropy source. The code path to verify randomness and add this data to the entropy pool just serves as a slowdown, but it can be disabled with:

echo 0 > /sys/block/sda/queue/add_random

This will work with Linux 2.6.36 and above.

Reducing writes

Reduce Firefox's Session Saving frequency

Reduce Firefox's Session Saving frequency mentions to alter the default of 15s to 60s, or perhaps 300s (5 minutes). In about:config, set browser.sessionstore.interval to 60000.

Remounting temporary files as tmpfs

To /etc/fstab:

none /tmp tmpfs defaults,noatime,mode=1777,size=1024M 0 0
none /var/tmp tmpfs defaults,noatime,mode=1777,size=512M 0 0

/var/lock and /var/run on a RAM disk

Ubuntu puts /var/lock and /var/run into a RAM disk; you can do the same with Debian by configuring the appropriate settings in /etc/default/rcS:

   1 cat << EOF >> /etc/default/rcS
   2 RAMRUN=yes
   3 RAMLOCK=yes
   4 EOF

This may break some buggy packages.

Creating aligned filesystems

This assume that the underlying partitions (including layers, such as LVM) have been created on properly-aligned sector boundaries.

These assume a 128 KiB erase block size.

More information:

• Aligning filesystems to an SSD's erase block size (Theodore Ts'o)

ext4

mkfs -t ext4 -E stripe-width=32,resize=$(FILESYSTEM_SIZE)*10G /dev/sda1

Set the resize parameter to 10 times the filesystem's size, assuming that in the future you might grow the filesystem that large. The default multiplier is 1000, which is definitely unreasonable. Remember to append 'G' for gigabytes.

Source: Aligning filesystems to an SSD's erase block size

This can also be down at mount time:

mount -t ext4 -o stripe=32 /dev/sda1

The stripe parameter multiplied by kernel's page size (4 KiB) will be the erase block size. I.e. 32 * 4 KiB = 128 KiB.

XFS

mkfs -t xfs -d su=128k -d sw=1 /dev/sda1

This can also be done at mount time, though the options/units are different:

mount -t xfs -o sunit=256,swidth=256 /dev/sda1

NILFS2

I believe this log-structured filesystem, by default, will already by aligned… For creation:

sudo mkfs -t nilfs2 -L 'Round OCZ Rally' /dev/sdi1

UDF

Not really block-aligned, but:

dd if=/dev/zero of=/dev/sdc bs=1M count=1
mkudffs -b 512 --media-type=hd /dev/sdc

btrfs

Creation

# RAID0 (mirrored metadata, striped data)
mkfs.btrfs -d raid0 /dev/sd[ef]1

Filesystem full

http://permalink.gmane.org/gmane.comp.file-systems.btrfs/17076

Filesystem full issue: plenty of unallocated space, but volume reports itself full. https://bugzilla.kernel.org/show_bug.cgi?id=74101

Secure Erase

SATA

   1 DEVICE=/dev/sda
   2 
   3 # Ensure "not frozen" appears
   4 # If frozen, it was done so by the BIOS; suspend/unsuspend the machine usually clears this state
   5 # Note the amount of time it will take to perform secure erase, e.g.
   6 # "4min for SECURITY ERASE UNIT. 8min for ENHANCED SECURITY ERASE UNIT."
   7 sudo hdparm -I ${DEVICE}
   8 
   9 # Set a temporary password
  10 hdparm --user-master user --security-set-pass password ${DEVICE}
  11 
  12 # If the drive supports enhanced security erase
  13 hdparm --user-master user --security-erase-enhanced password ${DEVICE}
  14 
  15 # and if not
  16 hdparm --user-master user --security-erase password ${DEVICE}

NVMe

See NVMe.