https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219688
Bug ID: 219688
Summary: [ZFS] zfs rename of mountpoint that is nfs shared
leaves old NFS configuration active and unremoveable
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: sbr...@freebsd.org
CC: allanj...@freebsd.org
In the world of "yeah, don't do that", I was renaming a bunch of zfs mount
points on my nfs server today.
'zfs rename mountpoint mountpoint.new'
These filesystems were NFS shared to host test machines for network style nfs
booting. After the zfs rename, the old entries still exist as indicated by the
NFS server whining about them and their existence in /etc/zfs/exports.
This in itself may not be a bug, as the computer did what I told it to do.
However, the old sharenfs settings for the old mountpoint are now immutable.
Since the old mountpoints don't exist, the error checking to see if the
mountpoints exist refuses to purge the nfs settings.
As a workaround, renaming the filesystems back to their old name allows me to
purge the old nfs settings.
I had thought just creating any old filesystem with the old name would allow me
to purge these settings, however it appears that the settings were set with
"legacy" options of some kind as I receive the error:
cannot unshare 'zroot/tftpboot/netboot_sysdev06': legacy share
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
