ZFS Unable to mount/rename filesystem when mount and procstat agree nothing is either mounted in the filesystem nor any file is opened

F

Ferocious1881

I am trying to rename a filesystem with rename a filesystem to another path, but I am getting the error
Code: 
cannot umount 'jails/acme': pool or dataset is busy
Uncomfortably I have already tested for inner mounts with mount | grep acme and have no fond other thing that the same filesystem that I am trying to umount. like wise I have tested the existence of opened files with fstat -v -f /jails/acme which shows nothing.
What is happening
 
Is that in the jail or from the host? I think you should be doing the zfs rename from the host, make sure the jail/jails are stopped/not mounted
 
If it is the same "acme" named jail from
forums.freebsd.org

bhyve - Jailed Bhyve: /dev/nmdm-acme.1B: No such file or directory. Should I make a problem report?

I have a jail with the configuration at /etc/jail.conf acme { exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.consolelog = "/var/log/jail_console_${name}.log"; allow.raw_sockets; allow.vmm; enforce_statfs = 2; securelevel = 2; exec.clean; mount.devfs; devfs_ruleset...
forums.freebsd.org forums.freebsd.org

the guest running in bhyve(8) may trigger that /dev/vmm/* and /dev/vmm.io/* (or perhaps /dev/nmdm-acme ?) still persist after a erogenous run attempt. Even the jail shut down it may still have an hold on those vmm devices .

Have you tried rebooting the host?
 
T-Daemon said:
If it is the same "acme" named jail from
forums.freebsd.org

bhyve - Jailed Bhyve: /dev/nmdm-acme.1B: No such file or directory. Should I make a problem report?

I have a jail with the configuration at /etc/jail.conf acme { exec.start = "/bin/sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.consolelog = "/var/log/jail_console_${name}.log"; allow.raw_sockets; allow.vmm; enforce_statfs = 2; securelevel = 2; exec.clean; mount.devfs; devfs_ruleset...
forums.freebsd.org forums.freebsd.org

the guest running in bhyve(8) may trigger that /dev/vmm/* and /dev/vmm.io/* (or perhaps /dev/nmdm-acme ?) still persist after a erogenous run attempt. Even the jail shut down it may still have an hold on those vmm devices .

Have you tried rebooting the host?
Click to expand...
No Idea what happened, but I was able to rename the filesystem
 
Have the problem again:
I confirmed to not have mount with mount | grep /jails/nfs, then make an index find /jails/nfs > index and check for open files cat index | xargs -L1 fstat | uniq
And got the following report
Code: 
USER     CMD          PID   FD MOUNT      INUM MODE         SZ|DV R/W NAME
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): Device busy
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: kinfo_getfile(): No such process
fstat: /jails/nfs/var/db/etcupdate/current/usr/share/nls/en_US.US_ASCII: No such file or directory
fstat: /jails/nfs/var/db/etcupdate/current/usr/share/nls/POSIX: No such file or directory
fstat: /jails/nfs/var/db/etcupdate/current/etc/os-release: No such file or directory
fstat: /jails/nfs/var/db/etcupdate/current/etc/rmt: No such file or directory
fstat: /jails/nfs/var/db/etcupdate/current/etc/unbound: No such file or directory
fstat: /jails/nfs/sys: No such file or directory
 
You must log in or register to reply here.
Back
Top