If you end up in the double-mounted situation mentioned below, use
mount -v to find the fsid for each double-mounted filesystem and then
umount them using the fsid.
To avoid this, always use the -R option (temporary, alternate root
mount point) with zpool if you are working with a root pool.
I doubt the issues you are encountering have much to do with ZFS.
It sounds like you are using TimeMachine over NFS. Obviously, Apple does not
support that configuration:
http://www.google.com/search?q=time+machine+nfs+site:apple.com
In my opinion, TimeMachine should only be used with block
AFP is not the same as HFS+. Time Machine will work better with AFP than NFS
or SMB/CIFS, but it's still not using native HFS+ unless you are using block
storage (even if you use AFP with an HFS+ filesystem).
Time Machine cannot function at all without accessing HFS+ directly. If you
are
increase and
decrease the size and doesn't mention anything special about Time Machine.
On Apr 28, 2011, at 5:02 PM, Daniel O'Connor wrote:
On 29/04/2011, at 2:16, Malcolm Waltz wrote:
I doubt the issues you are encountering have much to do with ZFS.
It sounds like you are using TimeMachine over
On Apr 28, 2011, at 6:08 PM, Jeremy Chadwick wrote:
Be aware there are all sorts of caveats/complexities with iSCSI on
FreeBSD. There are past threads on -stable and -fs talking about them
in great detail. I personally wouldn't go this route.
Why can't OS X use CIFS? It has the ability to
userlist_enable=YES
userlist_deny=NO
userlist_file=/usr/local/etc/vsftpd.user_list
check_shell=NO
Good luck,
Malcolm Waltz
Unix Systems Administrator III
Office of Information Technology
University of the Pacific
-Original Message-
From
On Jan 6, 2012, at 6:48 AM, David Magda wrote:
On Thu, January 5, 2012 14:28, Malcolm Waltz wrote:
I've included a working vsftpd.conf below for FTPES. For what you are
doing, you may not need all of these parameters. The pasv_ parameters are
mostly only necessary if you need to serve
