[DragonFlyBSD - Bug #2768] Slave HAMMER PFSes cannot be exported via NFS

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2768 has been updated by dillon.

File hammer43.patch added
Assignee changed from tuxillo to dillon

Well, I am still uncertain as to how this will effect the VFS cache.  I've included a new patch that basically does what is suggested... sets VPFSROOT as long as obj_id is HAMMER_OBJID_ROOT.  It appears to work in a quick test of a SLAVE.  The slave does not appear to be frozen on the export-side.  Note that the client-side mount will (should) be a snapshot of the SLAVE as-of when the mount is made, so the client will not see any updates the slave gets until it remounts it.  Also, if the history related to the snapshot it does is deleted through normal hammer cleanups, the existing mount will become unstable.

-Matt

----------------------------------------
Bug #2768: Slave HAMMER PFSes cannot be exported via NFS
http://bugs.dragonflybsd.org/issues/2768#change-12635

* Author: shamaz
* Status: In Progress
* Priority: Normal
* Assignee: dillon
* Category: Userland
* Target version: 4.2.x
----------------------------------------
The situation I already described in user mailing list: suppose you have
slave HAMMER PFS mounted at /nbackup and want to export it, so you add to
/etc/exports a line like this:

/nbackup -ro -network 192.168.10/24

When you restart mountd daemon you will get these errors in
/var/log/messages:

Jan 14 18:37:24 ressurected mountd[2279]: can't export /nbackup
Jan 14 18:37:24 ressurected mountd[2279]: bad exports list line /nbackup
-ro -network 192.168.10/24

Once PFS is upgraded to master, it can be exported fine.

---Files--------------------------------
test.c (398 Bytes)
hammer_inode.c.patch (685 Bytes)
hammer43.patch (810 Bytes)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account