search

fabioz23 / maczfs

Automatically exported from code.google.com/p/maczfs
Other
0 stars 0 forks source link

"zpool export" causes OS X Server 3.0.3 to complain about "Volume "{NAME}" not responding", affects File Sharing #136

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. MacZFS 74.3.3
2. "zpool export {NAME}"

What is the expected output? What do you see instead?
I expect that the volumes unmount quietly, and no error messages occur.

Instead, Mac OS X server immediately sends a notification for all mounted ZFS 
volumes, "Volume "{NAME}" not responding. The volume "{NAME}" is no longer 
accessible. Loss of this volume may affect services or applications on the 
server." This is sent via email and push notification if the appropriate 
options are set.

What version of the product are you using? On what operating system?
MacZFS 74.3.3 on 10.9.2.

Please provide any additional information below.
This may or may not be expected functionality because I share my ZFS volumes 
using OS X Server File Sharing. I have never tried a "zpool export" before, so 
I can't say exactly what happened with 74.1.0.
After this situation occurs, the ZFS volumes shared via AFP cannot be accessed, 
even though they appear as shared volumes.
As a workaround, "serveradmin stop sharing" "serveradmin start sharing" fixes 
the problem. In my case, I had to repeat the stop/start twice to get it working 
again.

Unless there's something that can be done during FS unmount to make the AFP 
server happy, the information here might just be appropriate for a FAQ.

Original issue reported on code.google.com by sbyt...@gmail.com on 1 Mar 2014 at 3:20

GoogleCodeExporter commented 9 years ago 
This answer is a bit speculative, I don't have a 10.9.2 to test, and sharing 
under 10.9.x is generally experimental.
The problem may happen because the umount forced by "zpool export" does not 
properly (or timely enough) propagate to the sharing service.  So once the 
sharing service tries to release the ZFS filesystems, these are already gone 
and therefore no longer "responding".
The suggested sequence is to either first stop all services that access the ZFS 
filesystems and then "zpool export", or to use diskutil to initiate the unmount 
("diskutil umount /path/to/zfs/fs").
Will add that to the FAQ.

Original comment by googlelogin@bjoern-kahl.de on 2 Mar 2014 at 12:16