On 12/12/06, James F. Hranicky <[EMAIL PROTECTED]> wrote:
Jim Davis wrote:
>> Have you tried using the automounter as suggested by the linux faq?:
>> http://nfs.sourceforge.net/#section_b
>
> Yes. On our undergrad timesharing system (~1300 logins) we actually hit
> that limit with a standard automounting scheme. So now we make static
> mounts of the Netapp /home space and then use amd to make symlinks to
> the home directories. Ugly, but it works.
This is how we've always done it, but we use amd (am-utils) to manage two
maps, a filesystem map and a homes map. The homes map is of all type:=link,
so amd handles the link creation for us, plus we only have a handful of
mounts on any system.
It looks like if each user has a ZFS quota-ed home directory which acts as
its own little filesystem, we won't be able to do this anymore, as we'll have
to export and mount each user directory separately. Is this the case, or is
there a way to export and mount a volume containing zfs quota-ed directories,
i.e., have the quota-ed subdirs not necessarily act like they're separate
filesystems?
This is definitely a feature I'd love to see, whereby one can share
the filesystem at a higher point in the tree (aka /pool/a/b, sharing
/pool/a, but have "b" as its own filesystem). I know this breaks some
of the sharing, but I'd love to have clients be able to mount /pool/a
and by way of that see b as well and not have that treated as a
separate share.
Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
