>The other reason is that the machine has been around for years, already >using UFS and quotas extensively. Over winter break we had time to >upgrade to Solaris 10 and migrate the volume from svm to zvol, but not >much more.There are a few thousand users on the machine. The thought of >transitioning to that many zfs 'partitions' in order to have per-user >quotas seemed daunting, not to mention the administrative re-training >needed (edquota doesn't work. du is reporting 3000 filesystems?! etc).
I'm assuming "df"? I think that the problem you are describing is a symptom of how existing tools and methods fall apart when confronted with huge numbers of filesystems, but only because more information if presented by "df" than you did before. I'd love to have an option to df which only reported pools, not filesystems. (rather than having to type "df -F ufs; zpool list") The same problem exists with automounted home directories (but only active directories are shown, again this is something ZFS may want to emulate) >IMO, the quota-per-file-system approach seems inconvenient when you get >past a handful of file systems. Unless I'm really missing something, it >just seems like a nightmare to have to deal with such a ridiculous >number of file systems. Why? What additional per-filesystem overhead from a maintenance perspective are you seeing? Casper _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
