> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of MichaelHoy
>
> If the “.zfs” subdirectory only exists as the direct child of the
> mount point then can someone suggest how I can make it visible lower
> down without requiring me (even if it were possible for 50k users) to
> make each users’ home folder a file system?
I know other people have suggested previous versions. This might get you
somewhere.
The solution I use in my environment is: I always "share" (via cifs) or
"export" (via nfs) the root of the filesystem. So the ".zfs" directory is
always accessible by whatever client is mounting it.
Assuming you have an automated script or group policy which pushes the "mount"
to all the clients, you should not have much difficulty in just mounting
peoples' home directories with a longer UNC path. \\server\tank\home\user
instead of \\server\home\user
Also, my users often forget ".zfs" and can't remember where to find snapshots.
I solve this in a ridiculously simple way, which I endorse:
ln -s .zfs/snapshot snapshot
Believe it or not, it works equally well for cifs and nfs clients.
For unix/linux clients, I also endorse zhist. Just simplifies and accelerates
finding snapshots.
> By way of a background, I’m looking at the possibility of hosting our
> students personal file space on OpenSolaris since the capacities
> required go well beyond my budget to keep investing in our NetApp kit.
I don't know what other options you may have. It's either continue investing
in the Netapp, or make the home paths work somehow with ZFS. I don't think
there's anything else out there.
Somebody might say "AFS." And hairy though it may be, it's possible that it
may benefit you. I don't know. I know only one thing: Anybody who has used
AFS either loves it or hates it.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
