testing trim on ssd not working (solved)-ongoing

[Just17]

thanks j18.
 now for the next issue i discovered . diskdrake lists the ssd as sda but when i look at the fstab file it lists the partitions on sdc. so the obvious question is: when editing the rc.local file do i use sda or sdc? i would venture you would want to use what the fstab file dictates as it is the actual config file and disdrake is only a gui.
  enlighten me

Post the terminal output from the command ....

Code: [Select]

blkid -c /dev/null
and the contents of the fstab file

[loudog]

sorry not as responsive as id like hotel management you know is a 24 hr job , anyway here are the cl returns:
ruby@localhost ~]$ su
Password:
[root@localhost ~]# blkid -c /dev/null
/dev/sda1: UUID="d1c07a82-231e-4c59-83b0-3974621f168f" TYPE="ext4"
/dev/sda2: UUID="b1e16be8-d609-4de0-acaa-29180fed2416" TYPE="swap"
/dev/sda3: UUID="78ae2f65-de71-41bf-86da-58f644ad011e" TYPE="ext4"
[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sdc1 :
UUID=d1c07a82-231e-4c59-83b0-3974621f168f / ext4 noatime,nodiratime,discard,errors=remount-ro 1 1
# Entry for /dev/sdc3 :
UUID=78ae2f65-de71-41bf-86da-58f644ad011e /home ext4 noatime,nodiratime,discard,errors=remount-ro 1 2
none /proc proc defaults 0 0
# Entry for /dev/sdc2 :
UUID=b1e16be8-d609-4de0-acaa-29180fed2416 swap swap defaults 0 0
none /dev/pts devpts defaults 0 0

[Just17]

If you examine the fstab entry, it is using the UUID of the partition to specify it.
That UUID is for /dev/sda1 as is apparent from the blkid output.

The comment

Code: [Select]

# Entry for /dev/sdc1 :
is only that - a comment.
The drive may have been 'seen' as /dev/sdc at the time the fstab was written, but that is one of the reasons the UUID is used to specify the correct partition, regardless the   /dev/   applied to it at any time.

The same applies to the other partitions on the drive.

So, there is nothing at all wrong there ....  the mention of /dev/sdc  was true at the time, but is not now.

I hope I have explained it properly .....

regards

[loudog]

so if i edit the fstab to reflect the actual sd# it will not change anything because the fstab is using th uuid# anyway . thats how i interpret your helpful reply.

[Just17]

so if i edit the fstab to reflect the actual sd# it will not change anything because the fstab is using th uuid# anyway . thats how i interpret your helpful reply.

All lines with a  #   at the beginning are ignored, and this is often used for including information.

So anything you put on such a line makes no difference.

It will make no difference to the OS if you change

Code: [Select]

# Entry for /dev/sdc1 :
to

Code: [Select]

# Entry for /dev/sda1 :
except the information is edited.

[loudog]

well thank you so much j18.   now on to the next issue, i guess its not an issue but more of a clairification . in some of the tutorials it suggests editing the fstab file using noatime and nodiratime. the debates i have investigated seem to indicate that noatime includes nodiratime in of itself. how does pclos interpret these?

[Just17]

well thank you so much j18.   now on to the next issue, i guess its not an issue but more of a clairification . in some of the tutorials it suggests editing the fstab file using noatime and nodiratime. the debates i have investigated seem to indicate that noatime includes nodiratime in of itself. how does pclos interpret these?

They are there, as I understand it, to reduce unnecessary accesses to the drive.

atime =>  Access time ...  each accessed file would be updated at every access without the noatime mount entry. (in fact I think that relatime is now the default for later kernels ...  someone else would have to confirm or correct that 

If you right click on a file, select properties and then check the information you will find when that file was last accessed.
With the noatime entry this info is not updated each time thus saving writes to the drive.

EDIT:   Just read your question again ......  I am not sure about the noatime in PCLOS (whether it includes nodiratime or not), but, IMO, it does no harm to have nodiratime specified 
Maybe someone who knows will read this and comment.


regards