Considering that /tmp can get full, and/or be extremely active, you may not want to do this. Which is easier to add, storage or disk? As I said, unless there are very good performance-related reasons to do this, I probably wouldn't.
/tmp should never be part of your root file system, regardless of the architecture. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern Sent: Monday, June 27, 2005 5:45 PM To: [email protected] Subject: Re: /tmp as a logical volume My thinking was that /tmp on real dasd requires REAL DASD and if it is still part of the / dasd allocation, it is in addition to the space that /sbin, /bin, /lib, /lib64, /etc, etcerta take away from what we allocate for a customer's server machine. If /tmp is a vdisk then it should only take up real pages in main/xstore/paging_dasd when it is really used by some program in the server and its contents are not required across IPLs. /Tom --- "Post, Mark K" <[EMAIL PROTECTED]> wrote: > Why is using expanded storage for work files preferable to using real > disk? Unless you've got performance requirements for an application > that require vdisk for /tmp, I wouldn't do that. (And that would have > to be a pretty strange application.) > > > Mark Post > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Thomas Kern > Sent: Wednesday, June 22, 2005 8:50 AM > To: [email protected] > Subject: Re: /tmp as a logical volume > > > I was thinking that putting /tmp on a vdisk like we do with swap would > be better than lvm or a separate minidisk. What are the advantages of > having /tmp on real dasd? > > /Tom Kern > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
