On Tue, Jan 10, 2017 at 09:46:30PM +0100, Alexander Bluhm wrote:
> When I force to unmount a filesystem where another mountpoint is
> located, an unlinked mountpoint will remain. I have not found a
> way to restore the kernel to a sane state.
>
> ok?
anyone?
bluhm
Index: kern/vfs_syscalls.c
==
On Tue, Jan 10, 2017 at 09:46:30PM +0100, Alexander Bluhm wrote:
> The fix could be to unmount recursively.
Recursion in the kernel is bad. Root could create deeply nested
mount points and hit the stack limit when unmounting the tree.
I have converted the recursion to a list.
ok?
bluhm
Index:
On Wed, Jan 11, 2017 at 10:20:17AM -0800, patrick keshishian wrote:
> does
>
> # umount /dev/vnd1a
>
> not do the trick?
No.
I have written a test to create the problem.
# cd /usr/src/regress/sys/kern/mount
# make
...
# mount
/dev/sd0a on / type ffs (local)
/dev/vnd0b on /mnt/b type ffs (local
my initial attempt to send a response is not moving out of the
queue...so here is a second attempt.
On 1/10/17, Alexander Bluhm wrote:
> Hi,
>
> When I force to unmount a filesystem where another mountpoint is
> located, an unlinked mountpoint will remain. I have not found a
> way to restore the
Hi,
When I force to unmount a filesystem where another mountpoint is
located, an unlinked mountpoint will remain. I have not found a
way to restore the kernel to a sane state.
# mount /dev/vnd0a /mnt
# mkdir /mnt/mnt
# mount /dev/vnd1a /mnt/mnt
# mount
/dev/sd0a on / type ffs (local)
/dev/vnd0a
