[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

2022-12-12 Thread Ahmet Sait
This seems related to FITRIM implementation of ntfs-3g driver rather than 
fstrim:
https://github.com/util-linux/util-linux/issues/1929#issuecomment-1346176771

** Bug watch added: github.com/util-linux/util-linux/issues #1929
   https://github.com/util-linux/util-linux/issues/1929

** Package changed: util-linux (Ubuntu) => ntfs-3g (Ubuntu)

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

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

Status in ntfs-3g package in Ubuntu:
  Confirmed

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 root0.00 B/s0.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

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+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


[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

2022-11-26 Thread Ahmet Sait
See: https://askubuntu.com/questions/1442510/system-hangs-breaks-when-
fstrim-runs-dual-boot-on-ssd-setup for more details about my system
where this bug occurs.

-- 
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 a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  Confirmed

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 root0.00 B/s0.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

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

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


[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

2022-11-26 Thread Ahmet Sait
** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

-- 
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 a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  Confirmed

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 root0.00 B/s0.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

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

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