Re: getting "device busy" on smbfs mounted area
Hi Mark, Try the lsof command to display open files : lsof +D /p2dev >From the man page : > +D This option causes lsof to search for all open instances of directory D > and all the files and directories > it contains to its complete depth. > > Processing of the +D option does not follow symbolic links > within D unless the -x or -x l option is also > specified. Nor does it search for open files on file > system mount points on subdirectories of D unless > the -x or -x f option is also specified. [...] Regards, Dominic Coulombe On Fri, Mar 20, 2009 at 12:17, Mark D Vandale wrote: > In our fstab we mount a smbfs filesystem on z/OS.. It works for a while > but at some point we are getting hung up. I have no idea what's causing > this. Executing any cmd against it hangs for a while and the returns this > device busy message. Is there a way to get around this or force it to be > unmounted ? > > zlnx1a04:~ # umount /p2dev > umount: /p2dev: device is busy > > > Thanks, > > Mark Vandale > > -- > 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
Re: getting "device busy" on smbfs mounted area
You could try umount -l /p2dev (lazy unmount) Scott On Fri, Mar 20, 2009 at 10:17 AM, Mark D Vandale wrote: > In our fstab we mount a smbfs filesystem on z/OS.. It works for a while > but at some point we are getting hung up. I have no idea what's causing > this. Executing any cmd against it hangs for a while and the returns this > device busy message. Is there a way to get around this or force it to be > unmounted ? > > zlnx1a04:~ # umount /p2dev > umount: /p2dev: device is busy > > > Thanks, > > Mark Vandale > > -- > 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
getting "device busy" on smbfs mounted area
In our fstab we mount a smbfs filesystem on z/OS.. It works for a while but at some point we are getting hung up. I have no idea what's causing this. Executing any cmd against it hangs for a while and the returns this device busy message. Is there a way to get around this or force it to be unmounted ? zlnx1a04:~ # umount /p2dev umount: /p2dev: device is busy Thanks, Mark Vandale -- 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: Device busy
Werner, This has been experienced previously. If you're "adding" a new control unit to an LPAR, you have to manually configure it online to the LPAR before it can be used. For MVS, etc., this can be done by the operating system, but you'll probably need to do it from the service console. Mark Post -Original Message- From: Werner Kuehnel [mailto:werner.kuehnel@;mannheimer.de] Sent: Monday, November 11, 2002 6:05 AM To: [EMAIL PROTECTED] Subject: Device busy I installed Linux (SLES for S/390) onto 3 3390-3 volumes some months ago and got it started from disk. When trying to restart last week I discovered that the 3 volumes were no longer accessible by the Linux LPAR, sometime the configuration changed. So I changed the IODF/IOCDS dynamically to allow the Linux LPAR access to only the 3 volumes and the OSA and OSA-Express devices (chpids are of course shared by EMIF). After starting the LOAD at HMC the following message appear: "The load control unit and device is busy. The load control unit and device may be shared by another system." The 3 volumes are offline and has no logical paths in all running LPARs. All other LPARs are deactivated. I've searched all archives, fora and redbooks, well, there are some hits, mostly with IPL from tape, but couldn't find yet any hint how to overcome this problem. I'd really appreciate any help. Thanks, Werner -- _ Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany "Besuchen Sie uns im Internet: http://www.mannheimer.de";
Re: Device busy
No, just one CEC. I also believe that a POR would do the job, but I fear I won't get the time for a POR :-( I'd like to know if this is a consequence of dynamically changing the access to the devices and OS/390 2.10 or JES3 doesn't really give them free, although they're offline. Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany "McKown, John" wrote: > > Ouch! That hurts. I'm at a loss. I am fairly sure that a POR of the box will > clear the condition. But that is very extreme and likely to get other people > a bit upset at you . Do you have more than one CEC? Could another CEC > have the device "tied up"? > > -- > John McKown > Senior Technical Specialist > UICI Insurance Center > Applications & Solutions Team > +1.817.255.3225 > --
Re: Device busy
Ouch! That hurts. I'm at a loss. I am fairly sure that a POR of the box will clear the condition. But that is very extreme and likely to get other people a bit upset at you . Do you have more than one CEC? Could another CEC have the device "tied up"? -- John McKown Senior Technical Specialist UICI Insurance Center Applications & Solutions Team +1.817.255.3225 -Original Message- From: Werner Kuehnel [mailto:werner.kuehnel@;mannheimer.de] Sent: Monday, November 11, 2002 8:17 AM To: [EMAIL PROTECTED] Subject: Re: Device busy Hi John, just tried it, not even with a RESET CLEAR it works. Werner
Re: Device busy
Hi John, just tried it, not even with a RESET CLEAR it works. Werner "McKown, John" wrote: > > Werner, > I got something like that on an OS/390 IPL attempt. The same message, and > the devices in question were "off line" to all other LPARs. I then did a > "reset clear" on the LPAR that I was attempting to IPL, then IPL'ed it > again. This time it worked! It appears that the microcode assumed that the > IPL was still being attempted, even after the error message was displayed. > The "RESET CLEAR" cleared up the problem. > > -- > John McKown > Senior Technical Specialist > UICI Insurance Center > Applications & Solutions Team > +1.817.255.3225 > > > -Original Message- > From: Werner Kuehnel [mailto:werner.kuehnel@;mannheimer.de] > Sent: Monday, November 11, 2002 5:05 AM > To: [EMAIL PROTECTED] > Subject: Device busy > > > I installed Linux (SLES for S/390) onto 3 3390-3 volumes some months ago and > got it started from disk. When trying to restart last week I discovered that > the 3 volumes were no longer accessible by the Linux LPAR, sometime the > configuration changed. So I changed the IODF/IOCDS dynamically to allow the > Linux LPAR access to only the 3 volumes and the OSA and OSA-Express devices > (chpids are of course shared by EMIF). After starting the LOAD at HMC the > following message appear: "The load control unit and device is busy. The > load control unit and device may be shared by another system." The 3 volumes > are offline and has no logical paths in all running LPARs. All other LPARs > are deactivated. I've searched all archives, fora and redbooks, well, there > are some hits, mostly with IPL from tape, but couldn't find yet any hint how > to overcome this problem. > > I'd really appreciate any help. > > Thanks, > Werner > -- > > _ > > Werner Kuehnel > IMD GmbH (Mannheimer Versicherung) > Mannheim - Germany > > "Besuchen Sie uns im Internet: http://www.mannheimer.de"; -- _ Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany "Besuchen Sie uns im Internet: http://www.mannheimer.de";
Re: Device busy
Werner, I got something like that on an OS/390 IPL attempt. The same message, and the devices in question were "off line" to all other LPARs. I then did a "reset clear" on the LPAR that I was attempting to IPL, then IPL'ed it again. This time it worked! It appears that the microcode assumed that the IPL was still being attempted, even after the error message was displayed. The "RESET CLEAR" cleared up the problem. -- John McKown Senior Technical Specialist UICI Insurance Center Applications & Solutions Team +1.817.255.3225 -Original Message- From: Werner Kuehnel [mailto:werner.kuehnel@;mannheimer.de] Sent: Monday, November 11, 2002 5:05 AM To: [EMAIL PROTECTED] Subject: Device busy I installed Linux (SLES for S/390) onto 3 3390-3 volumes some months ago and got it started from disk. When trying to restart last week I discovered that the 3 volumes were no longer accessible by the Linux LPAR, sometime the configuration changed. So I changed the IODF/IOCDS dynamically to allow the Linux LPAR access to only the 3 volumes and the OSA and OSA-Express devices (chpids are of course shared by EMIF). After starting the LOAD at HMC the following message appear: "The load control unit and device is busy. The load control unit and device may be shared by another system." The 3 volumes are offline and has no logical paths in all running LPARs. All other LPARs are deactivated. I've searched all archives, fora and redbooks, well, there are some hits, mostly with IPL from tape, but couldn't find yet any hint how to overcome this problem. I'd really appreciate any help. Thanks, Werner -- _ Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany "Besuchen Sie uns im Internet: http://www.mannheimer.de";
Device busy
I installed Linux (SLES for S/390) onto 3 3390-3 volumes some months ago and got it started from disk. When trying to restart last week I discovered that the 3 volumes were no longer accessible by the Linux LPAR, sometime the configuration changed. So I changed the IODF/IOCDS dynamically to allow the Linux LPAR access to only the 3 volumes and the OSA and OSA-Express devices (chpids are of course shared by EMIF). After starting the LOAD at HMC the following message appear: "The load control unit and device is busy. The load control unit and device may be shared by another system." The 3 volumes are offline and has no logical paths in all running LPARs. All other LPARs are deactivated. I've searched all archives, fora and redbooks, well, there are some hits, mostly with IPL from tape, but couldn't find yet any hint how to overcome this problem. I'd really appreciate any help. Thanks, Werner -- _ Werner Kuehnel IMD GmbH (Mannheimer Versicherung) Mannheim - Germany "Besuchen Sie uns im Internet: http://www.mannheimer.de";
