Here is a clue to the problem, I think: I attach volumes 2108-210a to system logged in as MAINT. When I q dasd free, I do not see these disks listed as free. I RLDE the EXTENT CONTROL file and log off MAINT (after I have replaced the user direct file for the guest in question). When I log on to the guest I get the "not linked" message. When I log back into MAINT and q dasd free, the disks in question are showing free again. This says to me I am not attaching them correctly. Am I on the right track?
On Sat, Aug 15, 2015 at 1:12 PM, Don Williams <donbwms.foru...@gmail.com> wrote: > ATTACH to SYSTEM would be the logical time to read the label, since VM > would need to validate the label in order to securely process LINK > requests. ATTACH to guest would not require validating label. > > I use to get confused between ATTACHing devices and LINKing minidisks. And > the difference between ATTACHing to SYSTEM and to a guest. > > On Sat, Aug 15, 2015 at 12:52 PM Neale Ferguson <ne...@sinenomine.net> > wrote: > > > I believe he's reformatted the disks and reattached to the system. My q > is > > when does the vol1 get re-read. In the old days it was after using: > > > > #CP VARY OFF rdev > > #CP VARY ON rdev > > > > But I seem to recall a change around VM/ESA that caused it to happen at > > attach time. > > > > > > -------- Original message -------- > > From: Mark Post <mp...@suse.com> > > Date: 2015/08/15 12:31 (GMT-05:00) > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: [LINUX-390] Adding DASD to a guest > > > > >>> On 8/15/2015 at 11:56 AM, Cameron Seay <cws...@gmail.com> wrote: > > > Any ideas why I'm seeing this? I went through the steps to format, > label > > > and attach these to guest lnx065... > > > > > > HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted > > > HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted > > > HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted > > > > Not sure how you're really trying to do this. The "not linked" message > > usually comes as a result of a LINK statement in USER DIRECT, not an > ATTACH > > command. The "volid ?????? not mounted" piece normally happens when the > > DASD volume is not ATTACHed to SYSTEM. > > > > > > 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 more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > ---------------------------------------------------------------------- > > 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 more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > ---------------------------------------------------------------------- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Cameron Seay, Ph.D. Department of Computer Systems Technology School of Technology NC A & T State University Greensboro, NC 336 334 7717 x2251 ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/