TRIM on everything?

[Cheesemill]

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda1 during installation
UUID=2e19524f-b028-4ef3-93a5-bed6757708fc /               ext4    defaults,noatime,nodiratime,discard,errors=remount-ro        0       1
# /DATA was on /dev/sdc1 during installation
# UUID=3A2084D220849713 /DATA           ntfs    defaults,umask=007,gid=46 0       0
# /SSD2DATA was on /dev/sdb1 during installation
UUID=de961735-1d84-4c72-8abe-fefa7b03a708 /SSD2DATA       ext4    defaults,noatime,nodiratime,discard,errors=remount-ro        0       2
# /home was on /dev/sda2 during installation
UUID=5a71aee7-cd8c-431f-bdc3-828bc40226b7 /home           ext4    defaults,noatime,nodiratime,discard,errors=remount-ro        0       2
# swap was on /dev/sdc2 during installation
UUID=c01746dc-7f90-40a6-9dda-324aecf9bdce none            swap    sw              0       0
# Place tmp into ram
tmpfs       /tmp        tmpfs       defaults,mode=1777      0   0
tmpfs       /var/tmp    tmpfs       defaults,mode=1777      0   0
tmpfs       /var/spool  tmpfs       defaults,mode=1777      0   0
tmpfs       /var/cache  tmpfs       defaults                0   0

There is no need to specify noatime and nodiratime.

Just using noatime implicitly specifies nodiratime as well.

[haqking]

There is no need to specify noatime and nodiratime.

Just using noatime implicitly specifies nodiratime as well.

Spookily enough I was reading an article this evening which was saying the same, I hadnt realised it was a subset, but i am finding conflicting information.

I am still looking into it, but cheers.

[Cheesemill]

You may want to look here where someone looks at the source code.

[haqking]

You may want to look here where someone looks at the source code.

ha, yeah i already had it open in a tab

Cheers

[dcstar]

swap shouldnt be on a SSD if you can help it, and wont support discard anyway

Rubbish, the code for "Discard" has been in the kernel for Swap partition processing for a while now. It is always used and is not a user option.

[haqking]

Rubbish, the code for "Discard" has been in the kernel for Swap partition processing for a while now. It is always used and is not a user option.

Interesting.

However it appears on the arch and debian wiki that it is a user option however ?

That being said Swap shouldnt be on a SSD where possible though which was my point, as for swap not being able to use it, i wasn't aware it could but it would appear that the user can define it.