My fstab= ext4  noatime,errors=remount-ro 0       1
I read through the solid_state_drive arch link and I think I should
check my logs for errors.

I checked the /etc/cron* dirs and saw no fstrim cron.weekly job.  That's
weird because I thought ubuntu defaulted to a cron.weekly fstrim job.
Now, I'm wondering whether the install knows the install drive is a SSD??

I looked on this 16.04 box (M.2 ssd as well, w/no issues) and I have a
cron.daily and cron.weekly jobs for fstrim!  I guess I should fix that. 

I manually ran the fstrim on the 18.04 box w/issues the other day and
saw 211 Gb trimmed.
Just now, I ran it again and would guess that it has been running idle
for 7 or 8 hours:
$ sudo fstrim -av
[sudo] password for don:
/: 211 GiB (226551054336 bytes) trimmed

Thanks,
Don


On 06/15/2018 01:04 AM, Ralf Mardorf wrote:
> On Thu, 14 Jun 2018 17:06:40 -0400, Daniel Wastak wrote:
>> UUID=[Your blkid here] /      ext4    noatime,errors=remount-ro
> I'm using "noatime" for partitions used to record realtime audio, but
> for anything else I stay with the default "relatime" for good reasons,
> see the mount manpage.
>
> [weremouse@moonstudio ~]$ lsb_release -d; man mount | grep 'relatime' -A2 | 
> tail -11 | head -3
> Description:  Ubuntu 16.04.4 LTS
>        relatime
>               Update inode access times relative to modify or change time.  
> Access time is only updated if the previous access time was earlier than the 
> current modify  or  change  time.
>               (Similar to noatime, but it doesn't break mutt or other 
> applications that need to know if a file has been read since the last time it 
> was modified.)
>
> I recommend to take a look at the Arch Wiki. I'm running Ubuntu 16.04.4
> in a systemd-nspawn container, actually the "host" is running Arch,
> however, Ubuntu does use systemd, too, so the hints regarding periodic
> vs continuous TRIM should apply to Ubuntu, too.
>
> https://wiki.archlinux.org/index.php/Solid_State_Drive
>
> [root@archlinux rocketmouse]# lsb_release -d; systemctl status fstrim.timer
> Description:  Arch Linux
> ● fstrim.timer - Discard unused blocks once a week
>    Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor 
> preset: disabled)
>    Active: active (waiting) since Fri 2018-06-15 06:12:19 CEST; 45min ago
>   Trigger: Mon 2018-06-18 00:00:00 CEST; 2 days left
>      Docs: man:fstrim
>
> Jun 15 06:12:19 archlinux systemd[1]: Started Discard unused blocks once a 
> week.
>
>


-- 
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/xubuntu-users

Reply via email to