$ /etc/rc.d/mountd onestart /etc/rc.d/mountd: WARNING: /etc/exports is not readable. Exit 1 Actually /etc/exports did not exist at all. And this was not a "WARNING", this was a fatal error, mountd did not start. Alsp, should it actually fail like this? I have ZFS and I plan to do all NFS exports from ZFS, so /etc/exports would never be used. -- Andriy Gapon
On Sat, Jan 10, 2009 at 6:20 AM, Andriy Gapon <avg@icyb.net.ua> wrote:> > $ /etc/rc.d/mountd onestart > /etc/rc.d/mountd: WARNING: /etc/exports is not readable. > Exit 1 > > Actually /etc/exports did not exist at all. > And this was not a "WARNING", this was a fatal error, mountd did not start. > > Alsp, should it actually fail like this? I have ZFS and I plan to do > all NFS exports from ZFS, so /etc/exports would never be used.Uh, mountd is used for nfsd, so I'm not sure why you're trying to do this... The reference to /etc/exports is being picked up from /etc/rc.d/mountd on this line: required_files="/etc/exports" and it's picking up the actual `does it exist?' test from: [gcooper@orangebox /usr/home/gcooper]$ grep -A 3 required_files /etc/rc.subr # required_files n If set, check for the readability of the given # files before running a (re)start command. # # required_modules n If set, ensure the given kernel modules are -- rcvar required_dirs required_files required_vars eval unset ${_arg}_cmd ${_arg}_precmd ${_arg}_postcmd case "$_file" in -- for _f in $required_files; do if [ ! -r "${_f}" ]; then warn "${_f} is not readable." if [ -z "$rc_force" ]; then Cheers, -Garrett
> Alsp, should it actually fail like this? I have ZFS and I plan to do > all NFS exports from ZFS, so /etc/exports would never be used.ZFS writes its own exports file to '/etc/zfs/exports' - as far as I can tell this is pretty much all that happens when you mark a filesystem as NFS shared under ZFS. Then mountd is started from rc like this: /usr/sbin/mountd -r -n /etc/exports /etc/zfs/exports (thats taken from 'ps' on one of my running systems) So you still need an empty /etc/exports to be there. ZFS will take care of managing it's own exports file, but thats all it seems to do - there is no magic ZFS seperate implementation of NFS as far as I know. -pete.
On Sat, Jan 10, 2009 at 7:24 AM, Garrett Cooper <yanefbsd@gmail.com> wrote:> On Sat, Jan 10, 2009 at 7:20 AM, Andriy Gapon <avg@icyb.net.ua> wrote: >> on 10/01/2009 17:18 Garrett Cooper said the following: >>> >>> s/same functionality/same basic functionality/. >>> Mind you, NFS is a networking filesystem. ZFS is a filestore >>> filesystem, more rooted to the local machine I thought, like UFS. >> >> I am well aware of this. The difference between UFS and ZFS is that for >> the former you have to maintain /etc/exports by hand and for the latter >> /etc/zfs/exports is automatically managed via zfs tools. >> >> Andriy Gapon > > Maybe a zmountd or equivalent script should be written for zfs and the > common code should be factored out for both cases? > -GarrettSorry -- wrong list (current -> stable) ><. -Garrett