Thats the issue we are trying to avoid if possible. If we could put /, /opt, /usr, /lib, etc. etc. into LVM, we won't have to guestimate how much disk we'll need from the outset. We could grow as needed.
In the x86 world, we've been putting / in LVM for years and have never had a problem. Is there something specific about z/VM that doesn't play well with / in LVM? I keep reading where it's not a good idea to put / in LVM, but can you (or someone else) define actually why it's not a good idea? Thanks, Ryan >>> On Thu, Aug 14, 2008 at 10:15 AM, in message <[EMAIL PROTECTED]>, Robert J Brenneman <[EMAIL PROTECTED]> wrote: > Leave it outside LVM. It's one less thing you'll get paged about at 3 AM on > Sunday. Use LVM for everything else, but leave / on a basic plain old > partition. > > > -- > Jay Brenneman > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
