>Mike Dotson <[EMAIL PROTECTED]> wrote: > >> Create 20k zfs file systems and reboot. Console login waits for all the >> zfs file systems to be mounted (fully loaded 880, you're looking at >> about 4 hours so have some coffee ready). > >Does this mean, we will get quotas for ZFS in the future? > >We need it e.g. for the Berlios fileserver. It will stay with UFS as long >as we did not find another quota solution.
Would it help if filesystems were much cheaper so you could use per user filesystems? To me, ZFS has not fullfilled the promise of "cheap filesystems"; cheap to create, but much more expensive to mount. Trigger mounts should fix that and one of the reason automount can cheaply create 1000s of mounts is that it simply sits and waits on /home and does not actually perform the mounts or even the bookkeeping associated with creating them. As zfs is by and large hierarchical in the same nature, an /export/home zfs filesystem would need only one trigger mount point (and a trigger mount could trigger other trigger mounts, clearly) But this also requires a further integration of ZFS and NFS; either the NFS clients will need to know how to traverse mount points (why does my NFS client need to know that I am sharing /export/home/<eachuser> when it really ought to know only about /export/home only?) But the further integration should minimally consist of NFS knowing how to share filesystems it does not yet know the filehandle off. So when you share /export/home/casper NFS should really only know that pathname; when someone requests the mount NFS should then trigger the mount simply by doing the appropriate getattr calls. Some of the issues with ZFS are not that ZFS is a departure from "the old ways"; but that the rest of the system needs to follow suit; ZFS is not yet integrated enough. What I personally do for ZFS loopback mounts, such as required for /tftpboot/I86PC.Solaris_11 on install server, is making them into auto_direct mounts. The existance of "/" in /etc/vfstab has always been a anomaly of sorts: the system knew what it was mounted and it needed to be told again? The filesystem "service" should know what to mount where and trigger mount points would be the only ones in existance, initially. Casper _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
