Mike Gerdts wrote: ... >> Perhaps ZFS would never actually write >> these files, so maybe this wouldn't be an issue with ZFS though. From >> what I've seen, /var/tmp typically has a lot of small files in it anyway, >> many of them zero length. > > And on the other end of the spectrum are files that are huge that have > been sitting there for years with no one ever cleaning them up. I > think that there is a compelling case for making /var/tmp its own file > system (rpool/var/tmp) with a quota on it (to limit overall size) or > perhaps user quotas (to discourage irresponsible use). Those that > argue for a separate /var to get noexec,nodevices may like to set > those properties on /var/tmp and not worry so much about a separate > /var.
These are nice ideas that reflect the new spaces into which this can grow but I suspect that a quota is going too far for a default image. We've all spent the last N years doing single partition installs because disks grew to the point where that was the best thing to do (unless you really wanted 100G of space disk in /export/home.) I have one question for you and this proposal from Sanjay: What happens when an application stores peristent data under a shared directory in /var and there are multiple BEs that have their own version of this application and the binary data format is not compatible? Darren
