On 28/02/2019 13.25, Felix Miata wrote:
Carlos E. R. composed on 2019-02-28 12:07 (UTC+0100):
fstrim -av
# fstrim -av /disks/boot: 0 B (0 bytes) trimmed /: 0 B (0 bytes) trimmed
I tried on mine: Telcontar:~ # fstrim -av /other/ssd-test: 3.8 GiB (4092694528 bytes) trimmed /boot: 928.1 MiB (973135872 bytes) trimmed /: 99.1 GiB (106444374016 bytes) trimmed Telcontar:~ # As you see, my three partitions on that disk are trimmed - except swap (I don't know why). I'm surprised at the amount listed for /other/ssd-test, as I have not used that partition in months. Telcontar:~ # df -h /other/ssd-test /boot / Filesystem Size Used Avail Use% Mounted on /dev/sde3 15G 11G 3.8G 75% /other/ssd-test /dev/sde4 1011M 77M 883M 9% /boot /dev/sde5 148G 49G 92G 35% / Telcontar:~ # A second attemp reports: Telcontar:~ # fstrim -av /other/ssd-test: 0 B (0 bytes) trimmed /boot: 0 B (0 bytes) trimmed /: 313.8 MiB (328978432 bytes) trimmed Telcontar:~ # I suspect that in your case, trimming is disabled. You could try lsblk --discard in my case: Telcontar:~ # lsblk --discard /dev/sde NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sde 0 512B 2G 0 ├─sde1 0 512B 2G 0 ├─sde2 0 512B 2G 0 ├─sde3 0 512B 2G 0 ├─sde4 0 512B 2G 0 └─sde5 0 512B 2G 0 Telcontar:~ # Check your mount options. If you use LVM or encryption, things change, too. For example: Isengard:~ # fstrim -av /: 376 MiB (394194944 bytes) trimmed /home doesn't appear, it is encrypted. Isengard:~ # lsblk --discard /dev/sda NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO sda 0 512B 2G 0 ├─sda1 0 512B 2G 0 ├─sda2 0 512B 2G 0 ├─sda3 0 512B 2G 0 ├─sda4 0 512B 2G 0 └─sda5 0 512B 2G 0 └─cr_home 0 0B 0B 0 Isengard:~ # Which is because I forgot to add the option "allow_discards" to /etc/crypttab, and I did not reboot the machine since I did.
I've emailed PNY, and ordered another brand. https://www.newegg.com/Product/Product.aspx?reviews=all&Item=N82E16820215167
I could slip this in as is right now https://www.newegg.com/Product/Product.aspx?Item=N82E16820156186 but its my only backup and it's over 6 months old. With the current as tenous as it is I hesitate to risk its current content by trying clone over it from the current.
Yes, that's reasonable. But why is the current disk so slow I don't understand. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)