I think that we need to use /etc/lvm/lvm.conf to limit what z/linux can see.
Sam -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Friday, May 08, 2009 11:41 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES 10 SP2 - where do I find documentation on Access Control Table (ACT) >>> On 5/8/2009 at 12:22 PM, Sam Bass <sam.b...@mclaneco.com> wrote: > We have a LPAR z/Linux SLES 10sp1 and a z/VM z/Linux SLES 10sp2. > > We don't want these to see each others disk (LVM). > Right now I have them on different channels on our z9. > > I found some old documentation on ACT but I cannot find exactly how to > use it. Are you talking about DASD volumes, or SCSI over FCP disks? If the latter, hopefully your SAN switch support N-port ID Virtualization (NPIV), which eliminates the problem of two separate LPARs or guests looking like the same system to the switch. If you're talking about DASD, then you just make sure your I/O gens don't have the other LPAR's volumes in it. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
