In article <pine.neb.4.64.1602101127560.1...@david.technoskunk.fur>,
John D. Baker <jdba...@mylinuxisp.com> wrote:
>On Wed, 10 Feb 2016 16:08:10 +0000 (UTC), chris...@astron.com (Christos
>Zoulas) wrote:
>
>ksh: pid 557 proc c1c6a87c vmspace/map c1903778 flags 4000
Ksh tries to open a file and gets stuck in genfs_lock.
>df: pid 4402 proc c18b9008 vmspace/map c19039f4 flags 4000
Df tries to stat the filesystem and is stuck in vfs_busy.
>firefox: pid 418 proc c18b91b8 vmspace/map c19030d8 flags 4001
Firefox tries to open a file and gets stuck in genfs_lock.
>firefox: pid 418 proc c18b91b8 vmspace/map c19030d8 flags 4001
Firefox tries to creat a file on nfs and is stuck in vfs_busy.
We don't really care much about sync, and other crap that happens during
shutdown
>amd: pid 5064 proc c1852004 vmspace/map c19034fc flags 0
Amd is trying to unmount a filesystem and is stuck in genfs_lock
And the million $ question is:
Is amd trying to unmount because of the shutdown, or because of the
periodic mount timeout? If the second, do we have a locking race
during unmount?
Unfortunately looks like you'll have to reboot and redo the test to
answer this.
christos
