Public bug reported:

The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
computer once a week (usually on Monday midnight) in the case of a dual
boot system installed on a SSD (Windows/Ubuntu) due to high IO overhead.
I also had several freeze at boot due to the same problem.

When the freeze occur I can open a tty terminal and type the command
iotop to see the process which use that amount of IO. It was mount.ntfs-
3g which point to my mount point to my Windows 10 install on my SSD.

When the freeze occur the system is not responsive for about 10-15
minutes.

I solved my issue by disabling the fstrim.timer entirely with this
command:

sudo systemctl disable fstrim.timer

I can reproduce the problem on my installation by launching the fstrim-
timer:

sudo systemctl start fstrim.timer

Imediately after launching fstrim.timer, iotop display this line at top,
with my Windows 10 mount point:

  TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
  893 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

----
Systemd 237-3ubuntu10.19
Ubuntu 18.04.2

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1823721

Title:
  systemctl fstrim.timer freeze computer with an SSD  with dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  New

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

    TID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
    893 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  ----
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823721/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to