[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2020-02-11 Thread Colin Ian King
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesystem To manage notific

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2020-02-11 Thread John Gallagher
@Colin this was indeed fixed by the backport of 4ecd55ea074217473f94cfee21bb72864d39f8d7, as we suspected it would be. I think this can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2020-02-11 Thread Colin Ian King
@John, I was wondering what to do about this bug report. Is it still an issue or shall I close it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused fi

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-09-02 Thread Colin Ian King
See also: https://wiki.ubuntu.com/Kernel/StableReleaseCadence and https://kernel.ubuntu.com/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesyst

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-09-02 Thread Colin Ian King
We generally have a 3 week release cycle on kernels, so if it's in -proposed it probably in the later 1-2 weeks of this cycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-09-02 Thread Colin Ian King
latter 1-2 weeks of this cycle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesystem To manage notifications about this bug go to: https://bugs

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-30 Thread John Gallagher
We are going to set a system with a 4.15.0-60 kernel from the -proposed repository to confirm that this fixes the issue. Colin, do you know when that kernel will make its way out of -proposed and become generally available? -- You received this bug notification because you are a member of Ubuntu

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-30 Thread Colin Ian King
That's really helpful to know John, thanks for the feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesystem To manage notifications abou

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-29 Thread John Gallagher
It looks like items are in rare cases being removed from the export cache's hash table without being removed from the queue. Once they are removed from the hash table, no downcall can complete the request, because the item can't be looked up in the hash table, leaving the item orphaned, along with

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-29 Thread John Gallagher
We used BPF/BCC to trace all refcount changes on all of the relevant mounts, and for each (struct mount*, stack) pair, kept track of the number of references acquired/released by that pair. Including the struct mount* in the key in our map make the map quite large, but allowed us to pare the output

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-07 Thread John Gallagher
We are still seeing this issue and still working on tracking it down. We've done some tracing to track all of the refcount changes by stack when this occurs. However, the refcount is manipulated from many different contexts, making it difficult to identify which increment is the odd one out. We ar

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-08-06 Thread Colin Ian King
Any updates on this issue? ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused fi

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-07-24 Thread Brad Figg
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832384 Title: Unable to unmount apparently unused filesystem To manage notifications about this bug go to: https://bugs.launchpad.

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-06-12 Thread John Gallagher
Thanks for taking a look. One of the things that is painful about debugging this issue is how long it takes to manifest. It would probably require several weeks of testing a particular kernel version without seeing the issue before we could be reasonably sure that the problem is fixed. Also, testin

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-06-12 Thread Colin Ian King
I had a quick look at there are quite a few differences between the Delphix ZFS git repo and the upstream ZFS git repo. Github states: "This branch is 376 commits ahead of zfsonlinux:master.". So: 1. Does this issue occur with stock ZFS rather than Delphix ZFS? 2. With the activity you are perfo

[Bug 1832384] Re: Unable to unmount apparently unused filesystem

2019-06-11 Thread Colin Ian King
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubunt