** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount apparently unused filesystem
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount
latter 1-2 weeks of this cycle
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount apparently unused filesystem
Status in linux package in Ubuntu:
See also: https://wiki.ubuntu.com/Kernel/StableReleaseCadence
and https://kernel.ubuntu.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount apparently
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
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 Kernel
That's really helpful to know John, thanks for the feedback.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount apparently unused filesystem
Status in
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
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
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
Any updates on this issue?
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount
** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832384
Title:
Unable to unmount apparently unused filesystem
Status in linux package in Ubuntu:
In Progress
Bug
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,
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
** 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
16 matches
Mail list logo
