On Fri, June 18, 2010 08:29, Sendil wrote: > I can create 400+ file system for each users, > but will this affect my system performance during the system boot up? > Is this recommanded or any alternate is available for this issue.
You can create a dataset for each user, and then set a per-dataset quota for each one: > quota=size | none > > Limits the amount of space a dataset and its descendents can > consume. This property enforces a hard limit on the amount of > space used. This includes all space consumed by descendents, > including file systems and snapshots. Setting a quota on a > descendent of a dataset that already has a quota does not > override the ancestor's quota, but rather imposes an additional > limit. Or, on newer revisions of ZFS, you can have one big data set and put all your users in there, and then set per-user quotas: > userqu...@user=size | none > > Limits the amount of space consumed by the specified > user. Similar to the refquota property, the userquota space > calculation does not include space that is used by descendent > datasets, such as snapshots and clones. User space consumption > is identified by the usersp...@user property. There's also a "groupquota". See zfs(1M) for details: http://docs.sun.com/app/docs/doc/819-2240/zfs-1m Availability of "userquota" depends on the version of (Open)Solaris that you have; don't recall when it was introduced. As for which one is better, that depends: per-user adds flexibility, but a bit of overhead. Best to test things out for yourself to see if it works in your environment. You could always split things up into groups of (say) 50. A few jobs ago, I was in an environment where we have a /home/students1/ and /home/students2/, along with a separate faculty/ (using Solaris and UFS). This had more to do with IOps than anything else. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
