Re: Adding DASD to a guest
I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest 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 -- 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/ -- 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/
Re: Adding DASD to a guest
what is the command for that? On Sat, Aug 15, 2015 at 12:18 PM, Neale Ferguson wrote: > I thought vol1 labels were read at vary on time but that may have changed > to attach/detach. Try varying the volume off/on and then attaching to the > system. > > Original message > From: Cameron Seay > Date: 2015/08/15 11:56 (GMT-05:00) > To: LINUX-390@VM.MARIST.EDU > Subject: [LINUX-390] Adding DASD to a guest > > 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 > > -- > 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/ > > -- > 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/
Re: Adding DASD to a guest
>>> On 8/15/2015 at 11:56 AM, Cameron Seay 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/
Re: Adding DASD to a guest
I thought vol1 labels were read when to ATTACH dev TO SYSTEM. Once ATTACHed to SYSTEM, then minidisk on that volume would be available to LINK to guests. On Sat, Aug 15, 2015 at 12:31 PM Mark Post wrote: > >>> On 8/15/2015 at 11:56 AM, Cameron Seay 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/
Re: Adding DASD to a guest
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 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 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/
Re: Adding DASD to a guest
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 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 > 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 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/
Re: Adding DASD to a guest
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 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 > 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 > > 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 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/
Re: Adding DASD to a guest
Yes, you need to ATTACH rdev SYSTEM Original message From: Cameron Seay Date: 2015/08/15 13:32 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Adding DASD to a guest 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 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 > 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 > > 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 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/ -- 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/
Re: Adding DASD to a guest
When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, MAINT. When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH with SYSTEM, the attach is to VM which allows VM to process LINKs to minidisks on that rdev. When you log off those ATTACHs remain. On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson wrote: > Yes, you need to ATTACH rdev SYSTEM > > Original message > From: Cameron Seay > Date: 2015/08/15 13:32 (GMT-05:00) > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] Adding DASD to a guest > > 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 > 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 > > 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 > > > 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 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/ > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO
Re: Adding DASD to a guest
Worked like a charm. Problem solved! Thanks folks! On Sat, Aug 15, 2015 at 1:52 PM, Don Williams wrote: > When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, MAINT. > When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH > with SYSTEM, the attach is to VM which allows VM to process LINKs to > minidisks on that rdev. When you log off those ATTACHs remain. > > On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson > wrote: > > > Yes, you need to ATTACH rdev SYSTEM > > > > Original message > > From: Cameron Seay > > Date: 2015/08/15 13:32 (GMT-05:00) > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: [LINUX-390] Adding DASD to a guest > > > > 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 > > > 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 > > > 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 > > > > 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 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/htbi
Re: Adding DASD to a guest
Glad we could help. On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay wrote: > Worked like a charm. Problem solved! Thanks folks! > > On Sat, Aug 15, 2015 at 1:52 PM, Don Williams > wrote: > > > When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, > MAINT. > > When you log off all the ATTACHs to MAINT are DEATTACHed. When you ATTACH > > with SYSTEM, the attach is to VM which allows VM to process LINKs to > > minidisks on that rdev. When you log off those ATTACHs remain. > > > > On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson > > wrote: > > > > > Yes, you need to ATTACH rdev SYSTEM > > > > > > Original message > > > From: Cameron Seay > > > Date: 2015/08/15 13:32 (GMT-05:00) > > > To: LINUX-390@VM.MARIST.EDU > > > Subject: Re: [LINUX-390] Adding DASD to a guest > > > > > > 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 > > > > > 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 > 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,
Re: Adding DASD to a guest
P.S. In order to do the format you need to attach to your guest. Then reattach to SYSTEM to allow LINKs to be processed. On Sat, Aug 15, 2015 at 1:58 PM Don Williams wrote: > Glad we could help. > > On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay wrote: > >> Worked like a charm. Problem solved! Thanks folks! >> >> On Sat, Aug 15, 2015 at 1:52 PM, Don Williams >> wrote: >> >> > When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, >> MAINT. >> > When you log off all the ATTACHs to MAINT are DEATTACHed. When you >> ATTACH >> > with SYSTEM, the attach is to VM which allows VM to process LINKs to >> > minidisks on that rdev. When you log off those ATTACHs remain. >> > >> > On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson >> > wrote: >> > >> > > Yes, you need to ATTACH rdev SYSTEM >> > > >> > > Original message >> > > From: Cameron Seay >> > > Date: 2015/08/15 13:32 (GMT-05:00) >> > > To: LINUX-390@VM.MARIST.EDU >> > > Subject: Re: [LINUX-390] Adding DASD to a guest >> > > >> > > 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 >> > > > > 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 >> 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:
Re: Adding DASD to a guest
Got it. VM is GREAT! On Sat, Aug 15, 2015 at 2:01 PM, Don Williams wrote: > P.S. In order to do the format you need to attach to your guest. Then > reattach to SYSTEM to allow LINKs to be processed. > > On Sat, Aug 15, 2015 at 1:58 PM Don Williams > wrote: > > > Glad we could help. > > > > On Sat, Aug 15, 2015 at 1:57 PM Cameron Seay wrote: > > > >> Worked like a charm. Problem solved! Thanks folks! > >> > >> On Sat, Aug 15, 2015 at 1:52 PM, Don Williams < > donbwms.foru...@gmail.com> > >> wrote: > >> > >> > When you ATTACH w/o keyword SYSTEM, you are ATTACHing to your guest, > >> MAINT. > >> > When you log off all the ATTACHs to MAINT are DEATTACHed. When you > >> ATTACH > >> > with SYSTEM, the attach is to VM which allows VM to process LINKs to > >> > minidisks on that rdev. When you log off those ATTACHs remain. > >> > > >> > On Sat, Aug 15, 2015 at 1:39 PM Neale Ferguson > >> > wrote: > >> > > >> > > Yes, you need to ATTACH rdev SYSTEM > >> > > > >> > > Original message > >> > > From: Cameron Seay > >> > > Date: 2015/08/15 13:32 (GMT-05:00) > >> > > To: LINUX-390@VM.MARIST.EDU > >> > > Subject: Re: [LINUX-390] Adding DASD to a guest > >> > > > >> > > 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 > >> > > > > 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 > >> 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 > >> > > > > > >> >
Re: Adding DASD to a guest
Volume labels are read at VARY ON and any time cylinder 0 is detached from a virtual machine, whether mdisk or dedicated dasd. Alan Altmark Senior Managing Consultant IBM Systems Lab Services Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- From:"Neale Ferguson" To:"" Date:Sat, Aug 15, 2015 12:19 PMSubject:Re: [LINUX-390] Adding DASD to a guest I thought vol1 labels were read at vary on time but that may have changed to attach/detach. Try varying the volume off/on and then attaching to the system. Original message From: Cameron Seay Date: 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] Adding DASD to a guest 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 -- 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/ -- 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/
Re: Adding DASD to a guest
Ouch. I typically work in the z/OS world where there is only VARY. Multiple systems (including systems that are not local VM guests) could have the same DASD device online. Those other systems could re-label the volume while the volume was online to VM but not attached. Then hours later I could attach that device and VM would use stale label information. While technically ATTACH is not varying a device online, it is conceptually close to that. Close enough that I expect many users assume that. What was the reason, the VM designers chose VARY ON and DEATTACH CYL 0? On Sat, Aug 15, 2015 at 9:36 PM Alan Altmark wrote: > Volume labels are read at VARY ON and any time cylinder 0 is detached from > a virtual machine, whether mdisk or dedicated dasd. > > Alan Altmark > Senior Managing Consultant > IBM Systems Lab Services > > >Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- > From:"Neale Ferguson" To:"" < > LINUX-390@VM.MARIST.EDU>Date:Sat, Aug 15, 2015 12:19 PMSubject:Re: > [LINUX-390] Adding DASD to a guest > I thought vol1 labels were read at vary on time but that may have > changed to attach/detach. Try varying the volume off/on and then attaching > to the system. Original message From: Cameron Seay Date: > 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: > [LINUX-390] Adding DASD to a guest 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 -- 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/ > -- 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/
Re: Adding DASD to a guest
P.S. For some unknown reason, I was consistently misspelling DETACH On Sat, Aug 15, 2015 at 10:17 PM Don Williams wrote: > Ouch. I typically work in the z/OS world where there is only VARY. > Multiple systems (including systems that are not local VM guests) could > have the same DASD device online. Those other systems could re-label the > volume while the volume was online to VM but not attached. Then hours later > I could attach that device and VM would use stale label information. While > technically ATTACH is not varying a device online, it is conceptually close > to that. Close enough that I expect many users assume that. What was the > reason, the VM designers chose VARY ON and DEATTACH CYL 0? > > On Sat, Aug 15, 2015 at 9:36 PM Alan Altmark > wrote: > >> Volume labels are read at VARY ON and any time cylinder 0 is detached >> from a virtual machine, whether mdisk or dedicated dasd. >> >> Alan Altmark >> Senior Managing Consultant >> IBM Systems Lab Services >> >> >>Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest --- >> From:"Neale Ferguson" To:"" < >> LINUX-390@VM.MARIST.EDU>Date:Sat, Aug 15, 2015 12:19 PMSubject:Re: >> [LINUX-390] Adding DASD to a guest >> I thought vol1 labels were read at vary on time but that may have >> changed to attach/detach. Try varying the volume off/on and then attaching >> to the system. Original message From: Cameron Seay Date: >> 2015/08/15 11:56 (GMT-05:00) To: LINUX-390@VM.MARIST.EDU Subject: >> [LINUX-390] Adding DASD to a guest 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 -- 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/ >> -- 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/
Re: Adding DASD to a guest
>>> On 8/15/2015 at 10:17 PM, Don Williams wrote: > What was the > reason, the VM designers chose VARY ON and DEATTACH CYL 0? I would say for the same reason a lot of decisions got made, way back when. Sharing DASD between disparate operating systems wasn't particularly "top of mind" to the developers. As Alan is always saying, if you think a change in behavior makes sense, a request for enhancement to IBM would be the best route to follow. 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/
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
On Wed, 2003-11-12 at 13:35, Eric Sammons wrote: > I am searching for ways to ensure maximum up time of my "z/Linux" > environment. As such, I am wondering, when adding dasd to the environment > is there a way to go from editing the zipl.conf file to dasdfmt without > rebooting. Currently, I add my device to zipl.conf and then execute zipl > followed by a reboot. I would like to eliminate the reboot. Sure. echo "add device range=" > /proc/dasd/devices (Assuming it's a 2.4 kernel) You'll still want to put it in zipl.conf, and rerun zipl, so that when you *do* reboot it's picked up, though. Adam
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
Using the following, which was provided to me, # echo "add device range=0206" > /proc/dasd/devices I took the liberty of modifing the command to have >> so that I don't blow away my devices file. I then execute the following dasdfmt command: dasdfmt -y -b 4096 -n 0206 dasdfmt: Unable to open device /dev/dasd/0206/device: No such file or directory My devices file looks like this: 0200(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 144000 blocks, 562 MB 0201(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 594000 blocks, 2320 MB 0202(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 594000 blocks, 2320 MB 0203(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 594000 blocks, 2320 MB 0204(ECKD) at ( 94: 16) is dasde : active at blocksize: 4096, 594000 blocks, 2320 MB 0205(ECKD) at ( 94: 20) is dasdf : active at blocksize: 4096, 594000 blocks, 2320 MB 0292(none) at ( 94: 24) is dasdg : unknown 0206(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 594000 blocks, 2320 MB Anyidea what is happening here? I have noticed that the dasdfmt command isn't cooperating in SLES8. Where if I execute format at the VM layer all is well. Thanks! Eric Sammons (804)697-3925 FRIT - Infrastructure Engineering
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
On Wed, 2003-11-12 at 14:10, Eric Sammons wrote: > Using the following, which was provided to me, > > # echo "add device range=0206" > /proc/dasd/devices > > I took the liberty of modifing the command to have >> so that I don't blow > away my devices file. Actually, it won't. It's not really a file, it's an ioctl interface in the /proc pseudo-filesystem. So > is safe in this case. >> works too, though, I think. > I then execute the following dasdfmt command: > > dasdfmt -y -b 4096 -n 0206 > dasdfmt: Unable to open device /dev/dasd/0206/device: No such file or > directory > 0206(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 594000 > blocks, 2320 MB > > Anyidea what is happening here? I have noticed that the dasdfmt command > isn't cooperating in SLES8. Where if I execute format at the VM layer all > is well. Yeah, I've seen this before too. Let me guess: this is real, honest-to-goodness virgin disk, that nothing has ever touched before, right? For some reason, Linux won't touch it unless it finds some magic goodie on it that CMS formatting it gives it. I don't know if low-level CP formatting, or just Label formatting, would do the trick as well. I'd say it's a bug in the DASD driver or the dasdfmt utility, but I don't really know; the workaround, as you've found, is to touch all your disks with CMS first. Adam
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
Why go through all the trouble? Just create the zipl.conf file with enough dasd devices in it to cover future expansion. I use devices 290-2AF so I have 32 devices created in zipl.conf. I may only use three or four of them, but who cares? When I want to add another device to a server, just log on to the server console and issue #CP LINK * 297 297 MR (for some reason, I can't use the hcp command to do this...) #CP DISC then do the dasdfmt, fdasd, etc. Works like a champ! Every time! Use the Best! Linux for Servers Macintosh for Graphics Palm for Mobility Windows for Solitaire. Gordon W. Wolfe, Ph.D. VM & Linux Systems Support Enterprise Servers, The Boeing Company (425)865-5940 > -- > From: Eric Sammons > Reply To: Linux on 390 Port > Sent: Wednesday, November 12, 2003 11:35 AM > To: [EMAIL PROTECTED] > Subject: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot > > I am searching for ways to ensure maximum up time of my "z/Linux" > environment. As such, I am wondering, when adding dasd to the environment > is there a way to go from editing the zipl.conf file to dasdfmt without > rebooting. Currently, I add my device to zipl.conf and then execute zipl > followed by a reboot. I would like to eliminate the reboot. > > Thank you! > Eric Sammons > (804)697-3925 > >
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
On Wed, 2003-11-12 at 14:38, Wolfe, Gordon W wrote: > Why go through all the trouble? Just create the zipl.conf file with enough dasd > devices in it to cover future expansion. I use devices 290-2AF so I have 32 devices > created in zipl.conf. I may only use three or four of them, but who cares? > > When I want to add another device to a server, just log on to the server console and > issue > > #CP LINK * 297 297 MR (for some reason, I can't use the hcp command to do this...) Wildcard expansion. Try hcp link \* 297 297 mr Adam
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
On Wed, 2003-11-12 at 21:10, Eric Sammons wrote: > dasdfmt -y -b 4096 -n 0206 > dasdfmt: Unable to open device /dev/dasd/0206/device: No such file or > directory The dasdfmt utility is assuming DEVFS active. You should use dasdfmt -f /dev/dasdh -b 4096 Rob
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
> When I want to add another device to a server, just log on to the server console and issue > #CP LINK * 297 297 MR (for some reason, I can't use the hcp command to do this...) > #CP DISC The reason you can't use the 'hcp' command to process your LINK statement as shown is the presence of the unescaped asterisk. Either escape it, or replace it with the uid of the guest machine ... it then works. Personally, I always opt for the latter. Regards, --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "A bird in hand is safer than one overhead."
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
Let me expand upon this some more. When I go to a CMS userid on a 3270 screen, I can issue the command CP SMSG VMTAPE VERSION and get the response VM:Tape 1.7C G0212 SP01 VMTBUF016I VERSION completion code=0. but in Linux SLES8, I can issue (from root) hcp smsg vmtape version and get no response. Why not? This is a class G CP command and VMTAPE should respond to anyone with this message. No escape characters needed or anything. I can do it from CMS userids that don't have IUCV statements in the directory, so that isn't a requirement. There are a lot of things I could do if I could use the SMSG command from within Linux via hcp. Use VMTAPE to mount a tape on a Linux server, for example. Use the Best! Linux for Servers Macintosh for Graphics Palm for Mobility Windows for Solitaire. Gordon W. Wolfe, Ph.D. VM & Linux Systems Support Enterprise Servers, The Boeing Company (425)865-5940 > -- > From: James Tison > Reply To: Linux on 390 Port > Sent: Wednesday, November 12, 2003 7:57 PM > To: [EMAIL PROTECTED] > Subject: Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a > reboot > > > When I want to add another device to a server, just log on to the server > console and issue > > #CP LINK * 297 297 MR (for some reason, I can't use the hcp command to > do this...) > > #CP DISC > > The reason you can't use the 'hcp' command to process your LINK statement > as shown is the presence of the unescaped asterisk. Either escape it, or > replace it with the uid of the guest machine ... it then works. Personally, > I always opt for the latter. > > Regards, > --Jim-- > James S. Tison > Senior Software Engineer > TPF Laboratory / Architecture > IBM Corporation > "A bird in hand is safer than one overhead." > >
Re: Adding DASD to a guest, going from zipl.conf to dasdfmt w/o a reboot
Well, ok, from apples to oranges we go ... Last time, you complained about bash (or any shell for that matter) interfering with the content of the message being sent to the VM CP. OK, that's fixable from the user's end. SMSG is a totally different beast. While it indeed is a Class G command, it's also designed to communicate special messages between guests, one that the receiver is programmed to deal with and maybe even reply to. Note the difference between the two on the initiator's end: your terminal will lock up on a CP command until the response + a READY is received; but you'll get back a READY from SMSG immedately. There's a reason for this: one protocol is synchronous, and the other (SMSG) isn't. That would be my guess as to why you don't see SMSG replies, but I'll betcha its author (Neale?) could jump in here and confirm (or not) that. I don't get responses from "hcp smsg" at my ssh terminal, either. But if I set myself as SECUSER to the Linux guest, I can see all the responses to my SMSGs on the CMS tube as SECUSER traffic. Big help, huh? Sorry, --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "A bird in hand is safer than one overhead."
Re: Adding DASD to a guest, going from zipl.conf to d asdfmt w/o a reboot
>> I then execute the following dasdfmt command: >> >> dasdfmt -y -b 4096 -n 0206 >> dasdfmt: Unable to open device /dev/dasd/0206/device: No such file or >> directory > >> 0206(ECKD) at ( 94: 28) is dasdh : active at blocksize: 4096, 594000 >> blocks, 2320 MB >> >> Anyidea what is happening here? I have noticed that the dasdfmt >> command isn't cooperating in SLES8. Where if I execute format at the >> VM layer all is well. >Yeah, I've seen this before too. >Let me guess: this is real, honest-to-goodness virgin disk, that nothing has ever touched before, right? > >For some reason, Linux won't touch it unless it finds some magic goodie on it that CMS formatting it gives it. I >don't know if low-level CP formatting, or just Label formatting, would do the trick as well. I'd say it's a bug >in the DASD driver or the dasdfmt utility, but I don't really know; the workaround, as you've found, is to touch >all your disks with CMS first. I've seen that before too - I bet it works if you use the dasdfmt command like this: dasdfmt -b 4096 -v -p -f /dev/dasdh Marcy Cortes Wells Fargo Services Co
Re: Adding DASD to a guest, going from zipl.conf to d asdfmt w/o a reboot
HCP is not going to capture the response from VMTAPE just a return code from CP. The VMTAPE guy uses CP MSG to send a response not a VMCF reply.
