automatic trim for ssd's default in trusty

[fooman]

saw this over at the discourse site....great news! i have been adding different options to set trim since using ssd's over the last year or so (cron job, adding discard to fstab, etc...). nice to know it will be enabled by default without having to edit anything after install!

http://discourse.ubuntu.com/t/ssds-a...y-default/1346

https://plus.google.com/107564545827...ts/D2SB1zxb9Z9

https://launchpad.net/ubuntu/+source....1-5.1ubuntu11

[VinDSL]

Yeah, I saw that -- very encouraging!

I bought my first SSD, last week.

First thing I did was invoke TRIM.

This seems to work out pretty well...

http://www.techrepublic.com/blog/lin...ge-with-linux/

I was wondering why they couldn't add something like this to +1 for testing.

Since you've been into this for awhile, what do you think of this guy's twist?!?!?

[ventrical]

I have been running my ssd on SandyBridge since 13.04 (without TRIM). Ahhh .. but Trusty will be set for TRIM by Default.

I don't see any performance issues at current. It runs instantaneously! Closest to a super-computer that Iv'e seen. My ssd is SATA 3 Gen. I am going to replace a 13.04 partition with Trusty. I read the link you posted. Are there any cautions about using TRIM with partitions?

[VinDSL]

I read the link you posted. Are there any cautions about using TRIM with partitions?

Only thing that concerns me is the 'discard' option in the fstab drive entry.

On several sites, I've read that whole blocks of data can magically disappear without warning, when you run this option.

Heh! I'll be using this SSD in my 'road warrior'. I don't need to puke a drive 3000 miles from home, you know?

[mc4man]

I wouldn't bother with discard in fstab, just let the new script do what it does (currently set to run weekly in cron
( I only use noatime in fstab here for my current ssd

[VinDSL]

I wouldn't bother with discard in fstab, just let the new script do what it does [...]

pitti (I assume Pitt) script?!?!?

http://people.canonical.com/~pitti/scripts/fstrim

[ventrical]

It says I have to enter the first LBA adress.

hdparm --read-sector [ADDRESS] /dev/sdX

and I get ..

root@ventrical-MS-7798:~# hdparm --fibmap tempfile

tempfile:
 filesystem blocksize 4096, begins at LBA 2048; assuming 512 byte sectors.
 byte_offset  begin_LBA    end_LBA    sectors
           0    9516032    9520127       4096
     2097152    9582592    9586687       4096
     4194304    9439232    9447423       8192
     8388608    9472000    9504767      32768
    25165824    9635840    9689087      53248
root@ventrical-MS-7798:~# hdparm --read-sector [2048] /dev/sdX
  read-sector: bad/missing sector value
root@ventrical-MS-7798:~# hdparm --read-sector [9516032] /dev/sdX
  read-sector: bad/missing sector value
root@ventrical-MS-7798:~#

So what did I do wrong?

Note. This is a fresh install of Trusty daily (seamless) so I am just testing to see if TRIM is running by default..

How to here :
https://sites.google.com/site/lightrush/random-1/checkiftrimonext4isenabledandworking

[ventrical]

I assume now that TRIM was not set by default in trusty daily-current install because there is no fstab directory.

[fooman]

It says I have to enter the first LBA adress.

hdparm --read-sector [ADDRESS] /dev/sdX

and I get ..

root@ventrical-MS-7798:~# hdparm --fibmap tempfile

tempfile:
 filesystem blocksize 4096, begins at LBA 2048; assuming 512 byte sectors.
 byte_offset  begin_LBA    end_LBA    sectors
           0    9516032    9520127       4096
     2097152    9582592    9586687       4096
     4194304    9439232    9447423       8192
     8388608    9472000    9504767      32768
    25165824    9635840    9689087      53248
root@ventrical-MS-7798:~# hdparm --read-sector [2048] /dev/sdX
  read-sector: bad/missing sector value
root@ventrical-MS-7798:~# hdparm --read-sector [9516032] /dev/sdX
  read-sector: bad/missing sector value
root@ventrical-MS-7798:~#

So what did I do wrong?

ventrical, in your example above (/dev/sdX) the "X" in sdX needs to be changed to reflect you ssd drive (sda, sdb, sdc...ect). also the read-sector should be the number directly under "begin LBA" but WITHOUT the brackets. so your hdparm --read-sector line should be as follows (assuming your drive is sda):

sudo hdparm --read-sector 9516032 /dev/sda

hope that helps

[Mateusz Stachowski]

I assume now that TRIM was not set by default in trusty daily-current install because there is no fstab directory.

This automatic TRIM in Trusty isn't achieved by adding discard to /etc/fstab but by running a weekly cron job and it was already pointed out by mc4man.

Read the changelog for util-linux that was linked in first post it has all that information.

https://launchpad.net/ubuntu/+source....1-5.1ubuntu11