Date: Mon, 14 Aug 2017 12:06:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221512] Contents of ZFS datasets invisible after being mounted inside a jail with nullfs (Even after a reboot!) Message-ID: <bug-221512-8-3aowWDoPps@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-221512-8@https.bugs.freebsd.org/bugzilla/> References: <bug-221512-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221512 tsuroerusu@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|New |Closed --- Comment #1 from tsuroerusu@gmail.com --- With a little bit of help, I managed to figure out what the problem was. It turned out that I had run, head first, into the wall of nullfs not operating across file systems. Thus inside the jail, the data was being saved to a regular directory on my "storage/cloud"-dataset (Mountpoint: /storage/cloud= ), whereas outside the jail the child file system "storage/cloud/bc", having b= een left empty, was mounted over the folder "bc" on "storage/cloud", where the files actually resided, thus "hiding" them from view outside the jail. A si= mple "zfs unmount storage/cloud/bc" revealed them. Anybody reading this in the future after a Google search: If you are using = ZFS and want to put a file system and all of its children into a jail then you cannot use nullfs. Instead you need to either change the actual mount point using "zfs set mountpoint=3D/jails/jail1/storage storage/path/to/filesystem= " or to attach the entire dataset to the jail, and allow it to be managed from within the jail using "zfs jail". I would like to propose that the man page for mount_nullfs contain a short sentence about nullfs not crossing file system boundaries. From what I can = tell by, admittedly, giving it a quick look, I didn't see anything about that, so it's possible that I simply missed it if it actually is in there. I apologize for any inconvenience caused by this report. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-221512-8-3aowWDoPps>