NFS export of HAMMER slave PFS
Antonio Huete Jiménez
tuxillo at quantumachine.net
Wed Jan 14 07:57:52 PST 2015
You're doing it right, there is a bug in mountd. Specifically mountd
tries to set the export flag on the filesystem by using mountctl(2) or
mount(2) but it's failing.
Can you please open a bug on the tracker and assign it to me?
I'll check it later.
Quoting Vasily Postnicov <shamaz.mazum at gmail.com>:
> I have a slave HAMMER PFS which is mounted at /nbackup. I want to export it
> via NFS over my local network (it has 3 machines with ip addresses
> 192.168.10.1-192.168.10.3), so I added this line to /etc/exports
> /nbackup -ro -network 192.168.10/24
> then I invoked:
> service mountd restart
> and got these lines in /var/log/messages:
> Jan 14 18:37:24 ressurected mountd: can't export /nbackup
> Jan 14 18:37:24 ressurected mountd: bad exports list line /nbackup
> -ro -network 192.168.10/24
> I checked it again with a newly created hammer filesystem (using vnode disk
> and 20GB zero-filled file) and a slave PFS, containing mirror of /tmp. It
> gave me the same result. Then I upgraded the PFS to master and mountd
> accepted it with no errors.
> So my question is: can I export a slave PFS or I have to upgrade it to
> master first? I mean only read access, of course. My DragonFly version:
> With best regards, Vasily Postnicov
More information about the Users