Re: kern/56329: nvme(4) takes long time to umount

[Paul Goyette <paul%whooppee.com@localhost>]

On Wed, 20 Apr 2022, J. Hannken-Illjes wrote:

> > All of my kernels have DEBUG and DIAGNOSTIC enabled.  I do not have
> > LOCKDEBUG.
>
> Could you try a kernel without DEBUG/DIAGNOSTIC and see if it makes
> a visible difference?

OK, I tried a 9.99.96 kernel with both DEBUG and DIAGNOSTIC turned
off.

I ran my usual home-brew version of bulk-package-building script,
with about 680 packages, in a chroot sandbox rooted on the nvme
device.

When the build finished, I removed the chroot environment with
no problem (so, the ``remnant on /tmp'' bug previously reported
is gone!).

I then tried to unmount the nvme itself.  It took more than 10
seconds before it reported EBUSY.  I guess I must have had some
process somewhere with a reference to the device.

So, the unmount did not complete, but it still took a long time
to fail.


+--------------------+--------------------------+----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:    |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost    |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost  |
| & Network Engineer |                          | pgoyette99%gmail.com@localhost |
+--------------------+--------------------------+----------------------+