Well, I am aware that /tmp can be mounted on swap as tmpfs and that this is 
really fast as most all writes go straight to memory, but this is of little to 
no value to the server in question.

The server in question is running 2 enterprise third party applications. No 
compilers are installed...in fact its a super minimal Solaris 10 core install 
(06/06). The reasoning behind moving /tmp onto ZFS was to protect against the 
occasional misdirected administrator who accidently fills up tmp while 
transferring a file or what have you. As I said its a production server, so we 
are doing our best to insulate it from inadvertent errors

When this server was build it was built with 8GB of swap on a dedicated slice. 
/tmp was left  on / (root) and later mounted on a zpool.

Is this dangerous given the server profile? Am i missing something here? Some 
other SUN engineers say that /tmp "is" swap and vice versa on Solaris, but my 
understanding is that my dedicated swap slice "is" swap and is not directly 
accessible. /tmp is just another filesystem that is happens to be mounted on a 
zpool with a quota so there is no fear of user/admin error. Based on how the 
system was setup is this a correct assertion?
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to