[Bug 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes

[MasterCATZ]

Ubuntu 22.04 Kernel 5.15's  and this issue still exists 
I really do wish someone would do something about this 

I have been waiting hours for a ~100meg file to finish writing to a NTFS partition 
and yep its almost midnight 
its a USB3 drive that I can read 400mbs from ... 

Every 2.0s: grep -e Dirty: -e Writeback: /proc...  aio: Sun Dec 12
23:25:38 2021

Dirty:              4820 kB
Writeback:             4 kB

what gets me is I can copy a 3 gig file , and the slow down will start
after 1 Gb when dirtybit limit is reached then it just trickles along at
kbs

this does not happen with fat32 , but I need NTFS for mounting Bootable ISO's 
I really should have just hoped on a windows PC and copied the files ..

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fuse in Ubuntu.
https://bugs.launchpad.net/bugs/1336184

Title:
  USB flash drive (NTFS) keeps writing for quite a while even after
  "Eject" completes

Status in fuse package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 14.04

  Nautilus version: 1:3.10.1-0ubuntu9.1

  Expected: After pressing "Eject" on a flash drive (formatted with NTFS
  -- haven't tried with FAT yet) I expected it to return only after
  flushing and unmounting the drive so the drive is completely safe to
  remove at that point

  What happened: "Eject" returned after a short while. The drive still
  kept writing for a long time. Mount shows the drive still mounted for
  the period while the flash drive keeps blinking though "df" does not
  show the drive anymore. Removing the drive at this point results in
  partial file write and NTFS filesystem damage (fixable with ntfsfix
  but dangerous).

  Steps to reproduce:

  1) Insert a flash drive (tried with NTFS mounted drive though I
  believe FAT will show similar behaviour though latter uses "flush"
  mount option so may not be that prominent)

  2) Try copying a large file. For testing use a size that will also mostly fit into filesystem cache so that real wait for writing is during unmount: dd if=/dev/zero of=/media/<user>/<drive>/test.out bs=1M count=1000
  <user> is the user name and <drive> the name where drive was mounted by nautilus as per the label.

  3) "Eject" the drive from nautilus context menu after dd command above
  returns.

  4) Eject returns shortly. However drive is still writing as seen by
  the blinking, or disk throughput in gkrellm, iostat. Also note that
  "mount" still shows the drive as mounted though "df" and other tools
  don't.

  I have confirmed the same issue exists on all similar file managers
  namely nemo and caja. Haven't filed bugs against those yet.

  For comparison, the gnome-disks system utility correctly unmounts,
  ejects and stops the drive (last one even powers down the drive so the
  LED on drive is switched off which one would expect nautilus "Eject"
  to also do) so it doesn't seem to be a bug in udisks2.

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