Re: CRON not running for specific user
Anacron is different then cron.. it's normally invoked by cron once a day .. maybe in /etc/cron.d? It should be the one running the cron.daily and weekly stuff.See /etc/anacrontab .. Anyway - you might see if there are already anacron processes running and kill them: ps -ef | grep anacron Scott Rohling On Mon, Jun 9, 2014 at 5:24 PM, Vitale, Joseph wrote: > Hello, > > Oracle schedules jobs via CRON. Looks like user was editing his CRON > with using "crontab -e". > > Had some messages showing cron was locked. See below. > > Restarted CRON, stopped/started CRON no improvement. I tried to schedule > a simple CRON as oracle, does not run, no mail message. > > CRON works Ok for root. > > Errors when CRON stopped for oracle: > Jun 3 03:01:01 anacron[20959]: Anacron started on 2014-06-03 > Jun 3 03:01:01 anacron[20959]: Job `cron.daily' locked by another > anacron - skipping > Jun 3 03:01:01 anacron[20959]: Job `cron.weekly' locked by another > anacron - skipping > Jun 3 03:01:01 anacron[20959]: Normal exit (0 jobs run) > > Simple CRON trying to run for Oracle: > 03 20 * * * echo hi > /tmp/oracle.test.cron > > > Thanks > Joe > > Joseph Vitale > Technology Services Group > Mainframe Operating Systems > 95 Christopher Columbus Drive > Floor 14 > Jersey City, N.J. 07302 > Work 201-395-1509 > Cell917-903-0102 > > > The information contained in this e-mail, and any attachment, is > confidential and is intended solely for the use of the intended recipient. > Access, copying or re-use of the e-mail or any attachment, or any > information contained therein, by any other person is not authorized. If > you are not the intended recipient please return the e-mail to the sender > and delete it from your computer. Although we attempt to sweep e-mail and > attachments for viruses, we do not guarantee that either are virus-free and > accept no liability for any damage sustained as a result of viruses. > > Please refer to http://disclaimer.bnymellon.com/eu.htm for certain > disclosures relating to European legal entities. > > -- > 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/
CRON not running for specific user
Hello, Oracle schedules jobs via CRON. Looks like user was editing his CRON with using "crontab -e". Had some messages showing cron was locked. See below. Restarted CRON, stopped/started CRON no improvement. I tried to schedule a simple CRON as oracle, does not run, no mail message. CRON works Ok for root. Errors when CRON stopped for oracle: Jun 3 03:01:01 anacron[20959]: Anacron started on 2014-06-03 Jun 3 03:01:01 anacron[20959]: Job `cron.daily' locked by another anacron - skipping Jun 3 03:01:01 anacron[20959]: Job `cron.weekly' locked by another anacron - skipping Jun 3 03:01:01 anacron[20959]: Normal exit (0 jobs run) Simple CRON trying to run for Oracle: 03 20 * * * echo hi > /tmp/oracle.test.cron Thanks Joe Joseph Vitale Technology Services Group Mainframe Operating Systems 95 Christopher Columbus Drive Floor 14 Jersey City, N.J. 07302 Work 201-395-1509 Cell917-903-0102 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- 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: NFS migration
You need the root option... root=clientid[:clientid...] Specifies which NFS clients have root access to the file system path. If you specify the root= option, you must specify at least one NFS client identifier. To exclude NFS clients from the list, prepend the NFS client identifiers with a minus sign (-). Offer Baruch On Jun 9, 2014 9:25 PM, "Jake anderson" wrote: > I have tried to export with anon=0 but still as a root fron linux I am > unable to change the owner. Not sure where I am missing. > > Jake > On 9 Jun 2014 22:49, "Offer Baruch" wrote: > > > Dns should work just fine... > > Just google for it... > > I think root= is the correct syntax... > > Server should be where you mount the nfs... > > > > Offer > > On Jun 9, 2014 7:03 PM, "Jake anderson" > wrote: > > > > > Hi, > > > > > > Yes this is a netapp exporting the nfs. Could you please provide me > whole > > > syntax ? we gave the DNS instead of serverip. Are there any difference > ? > > > > > > > > > On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch > > > wrote: > > > > > > > Is this a netapp exporting the nfs? > > > > If so you need the root= export option? > > > > If this is linux then you need the no_root_squash option... > > > > > > > > Offer Baruch > > > > On Jun 9, 2014 6:27 PM, "Jake anderson" > > > wrote: > > > > > > > > > Hi, > > > > > > > > > > We again exported the path as anon=0,unmounted and mounted, but > still > > > the > > > > > root level of user is unable to change the Ownership. > > > > > > > > > > > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie < > beatt...@uk.ibm.com > > > > > > > > wrote: > > > > > > > > > > > Jake anderson writes: > > > > > > > Recently we did a migration from one NFS storage server to > > another > > > > NFS > > > > > > > storage server. During this Migration all the copied File had > > > owners > > > > as > > > > > > > root. In the recent NFS storage server the FTP server option is > > no > > > > more > > > > > > > available so we have mounted the NFS storage to a linux running > > on > > > > > VMware > > > > > > > infra(as a ftp server). So when we try change the owner of any > > file > > > > > > > mounted to Linux we get a permission denied(Even when we try it > > as > > > > > root). > > > > > > > The message we get is "permission denied"(This is the only > > > message). > > > > > The > > > > > > ls > > > > > > > -l clearly gives that all the file has the owner as root. > > > > > > > > > > > > > > Has any undergone this situation ? Why a root cannot change the > > > > > > owner(root) > > > > > > > to someother ID ? > > > > > > > Since the files have the User and Group copied from previous > NFS > > > > > storage. > > > > > > > Aren't there anyways to change the Owner and Group from Linux ? > > > > > > > > > > > > It's the NFS server that's forbidding it. It's very common in all > > > > > > but the snazziest of NFS environments for the NFS server to > > "squash" > > > > > > the root user of NFS clients and treat it as an unprivileged, > > > > > > anonymous user. This avoids having a root user on any NFS client > > > > > > getting root-level access to all exported files on the server. > > > > > > > > > > > > For a Linux-based NFS server, the export options "root_squash" > > > > > > (which is the default) and "all_squash" (probably not the case > > here) > > > > > > do this. You need an explicit export option "no_root_squash" to > > allow > > > > > > root on the chosen NFS clients to be allowed to chown and access > > > > > > exported files as though they were uid 0 on the server. Other NFS > > > > > > servers or appliances may present the option differently. > > > > > > > > > > > > --Malcolm > > > > > > > > > > > > -- > > > > > > Malcolm Beattie > > > > > > Linux and System z Technical Consultant > > > > > > IBM UK Systems and Technology Group > > > > > > > > > > > > > > > -- > > > > > > 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: NFS migration
I have tried to export with anon=0 but still as a root fron linux I am unable to change the owner. Not sure where I am missing. Jake On 9 Jun 2014 22:49, "Offer Baruch" wrote: > Dns should work just fine... > Just google for it... > I think root= is the correct syntax... > Server should be where you mount the nfs... > > Offer > On Jun 9, 2014 7:03 PM, "Jake anderson" wrote: > > > Hi, > > > > Yes this is a netapp exporting the nfs. Could you please provide me whole > > syntax ? we gave the DNS instead of serverip. Are there any difference ? > > > > > > On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch > > wrote: > > > > > Is this a netapp exporting the nfs? > > > If so you need the root= export option? > > > If this is linux then you need the no_root_squash option... > > > > > > Offer Baruch > > > On Jun 9, 2014 6:27 PM, "Jake anderson" > > wrote: > > > > > > > Hi, > > > > > > > > We again exported the path as anon=0,unmounted and mounted, but still > > the > > > > root level of user is unable to change the Ownership. > > > > > > > > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie > > > > > wrote: > > > > > > > > > Jake anderson writes: > > > > > > Recently we did a migration from one NFS storage server to > another > > > NFS > > > > > > storage server. During this Migration all the copied File had > > owners > > > as > > > > > > root. In the recent NFS storage server the FTP server option is > no > > > more > > > > > > available so we have mounted the NFS storage to a linux running > on > > > > VMware > > > > > > infra(as a ftp server). So when we try change the owner of any > file > > > > > > mounted to Linux we get a permission denied(Even when we try it > as > > > > root). > > > > > > The message we get is "permission denied"(This is the only > > message). > > > > The > > > > > ls > > > > > > -l clearly gives that all the file has the owner as root. > > > > > > > > > > > > Has any undergone this situation ? Why a root cannot change the > > > > > owner(root) > > > > > > to someother ID ? > > > > > > Since the files have the User and Group copied from previous NFS > > > > storage. > > > > > > Aren't there anyways to change the Owner and Group from Linux ? > > > > > > > > > > It's the NFS server that's forbidding it. It's very common in all > > > > > but the snazziest of NFS environments for the NFS server to > "squash" > > > > > the root user of NFS clients and treat it as an unprivileged, > > > > > anonymous user. This avoids having a root user on any NFS client > > > > > getting root-level access to all exported files on the server. > > > > > > > > > > For a Linux-based NFS server, the export options "root_squash" > > > > > (which is the default) and "all_squash" (probably not the case > here) > > > > > do this. You need an explicit export option "no_root_squash" to > allow > > > > > root on the chosen NFS clients to be allowed to chown and access > > > > > exported files as though they were uid 0 on the server. Other NFS > > > > > servers or appliances may present the option differently. > > > > > > > > > > --Malcolm > > > > > > > > > > -- > > > > > Malcolm Beattie > > > > > Linux and System z Technical Consultant > > > > > IBM UK Systems and Technology Group > > > > > > > > > > > > -- > > > > > 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?
Re: RHEL 6.5 "golden image" configuration
DUH! Yep; the Linux admin is working on some automation scripts for the new "clone", and mentioned that he had "bounced" Linux several times before noticing the HCP messages. Since we have not yet set him up to issue XAUTOLOG commands from z/VM, and he never asked us to XAUTOLOG the guest, that seems the most plausible explanation. Thanks, -jc- > -Original Message- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott > Rohling > Sent: Monday, June 09, 2014 12:51 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: RHEL 6.5 "golden image" configuration > > Could it be this was from a reboot, rather then a boot from 'scratch'? > > Scott Rohling > > > On Mon, Jun 9, 2014 at 10:37 AM, Chase, John wrote: > > > Hi, All, > > > > We recently installed RHEL 6.5 on z/VM 6.2 using the latest edition of > > Michael MacIsaac's "Virtualization Cookbook", which is written around > > z/VM > > 6.3 and RHEL 6.4. > > > > We "cloned" a new Linux guest from our RHEL 6.5 "golden image", and > > one of our Linux admins noticed some "strange" messages in the clone's boot > > log: > > > > = Begin paste = > > part of the golden image configuration included a section on settings > > at boot time - see section 9.2.6 of the pdf. > > in looking at the boot log for ch2lqvpsx I see the following messages > > HCPDTV040E Device 0190 does not exist > > Error: non-zero CP response for command 'DET 190': #40 HCPDTV040E > > Device 0191 does not exist > > Error: non-zero CP response for command 'DET 191': #40 HCPDTV040E > > Device 019D does not exist > > Error: non-zero CP response for command 'DET 19D': #40 HCPDTV040E > > Device 019E does not exist > > Error: non-zero CP response for command 'DET 19E': #40 = End paste > > = > > > > The concern is over the HCPDTV040E messages for the MDISKs used at CMS > > logon time. > > > > The cited section of the "Cookbook" states: > > > > = Begin paste = > > In order for z/VM 6.3 to relocate guests between single system image > > (SSI) members, there must not be any links to CMS disks. The LNXDFLT > > PROFILE creates links to minidisks and assigns virtual device numbers > > 190, 191, 19D, and 19E. These addresses must be detached. > > The vmcp module is used to accomplish this. > > > > To do these two tasks, edit the /etc/rc.d/rc.local file, which is run > > at boot time: > > > > # cd /etc/rc.d > > # vi rc.local > > > > And add the following lines: > > > > #!/bin/sh > > # > > # This script will be executed *after* all the other init scripts. > > # You can put your own initialization stuff in here if you don't # > > want to do the full Sys V style init stuff. > > > > touch /var/lock/subsys/local > > chshut halt vmcmd logoff > > chshut poff vmcmd logoff > > modprobe vmcp > > vmcp det 190 > > vmcp det 191 > > vmcp det 19d > > vmcp det 19e > > > > The z/VM virtual machine should now be logged off when you halt or > > power off Linux. > > = End paste = > > > > The appearance of the HCPDVT040E messages seems to suggest that the > > CMS disks are already detached when the rc.local script issues the > > vmcp det xxx commands. If true, can anybody say when (and by whom or > > what process) those disks are detached, apparently before rc.local runs? > > Is that "new" > > for RHEL 6.5? > > > > TIA, > > > > -jc- > > > > ** > > Information contained in this e-mail message and in any attachments > > thereto is confidential. If you are not the intended recipient, please > > destroy this message, delete any copies held on your systems, notify > > the sender immediately, and refrain from using or disclosing all or > > any part of its content to any other person. > > > > -- > > 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/ ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any par
Re: RHEL 6.5 "golden image" configuration
Could it be this was from a reboot, rather then a boot from 'scratch'? Scott Rohling On Mon, Jun 9, 2014 at 10:37 AM, Chase, John wrote: > Hi, All, > > We recently installed RHEL 6.5 on z/VM 6.2 using the latest edition of > Michael MacIsaac's "Virtualization Cookbook", which is written around z/VM > 6.3 and RHEL 6.4. > > We "cloned" a new Linux guest from our RHEL 6.5 "golden image", and one of > our Linux admins noticed some "strange" messages in the clone's boot log: > > = Begin paste = > part of the golden image configuration included a section on settings at > boot time - see section 9.2.6 of the pdf. > in looking at the boot log for ch2lqvpsx I see the following messages > HCPDTV040E Device 0190 does not exist > Error: non-zero CP response for command 'DET 190': #40 > HCPDTV040E Device 0191 does not exist > Error: non-zero CP response for command 'DET 191': #40 > HCPDTV040E Device 019D does not exist > Error: non-zero CP response for command 'DET 19D': #40 > HCPDTV040E Device 019E does not exist > Error: non-zero CP response for command 'DET 19E': #40 > = End paste = > > The concern is over the HCPDTV040E messages for the MDISKs used at CMS > logon time. > > The cited section of the "Cookbook" states: > > = Begin paste = > In order for z/VM 6.3 to relocate guests between single system image (SSI) > members, there > must not be any links to CMS disks. The LNXDFLT PROFILE creates links to > minidisks and > assigns virtual device numbers 190, 191, 19D, and 19E. These addresses > must be detached. > The vmcp module is used to accomplish this. > > To do these two tasks, edit the /etc/rc.d/rc.local file, which is run at > boot time: > > # cd /etc/rc.d > # vi rc.local > > And add the following lines: > > #!/bin/sh > # > # This script will be executed *after* all the other init scripts. > # You can put your own initialization stuff in here if you don't > # want to do the full Sys V style init stuff. > > touch /var/lock/subsys/local > chshut halt vmcmd logoff > chshut poff vmcmd logoff > modprobe vmcp > vmcp det 190 > vmcp det 191 > vmcp det 19d > vmcp det 19e > > The z/VM virtual machine should now be logged off when you halt or power > off Linux. > = End paste = > > The appearance of the HCPDVT040E messages seems to suggest that the CMS > disks are already detached when the rc.local script issues the vmcp det xxx > commands. If true, can anybody say when (and by whom or what process) > those disks are detached, apparently before rc.local runs? Is that "new" > for RHEL 6.5? > > TIA, > > -jc- > > ** > Information contained in this e-mail message and in any attachments > thereto is confidential. If you are not the intended recipient, please > destroy this message, delete any copies held on your systems, notify the > sender immediately, and refrain from using or disclosing all or any part of > its content to any other person. > > -- > 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: RHEL 6.5 "golden image" configuration
John, If your Linux virtual machine IPL's CMS, is it done in the virtual machine's PROFILE EXEC, before Linux is IPLed? You could put a "CP Q 190 191 19D 19E" just before the "IPL " statement. -Mike MacIsaac On Mon, Jun 9, 2014 at 1:37 PM, Chase, John wrote: > Hi, All, > > We recently installed RHEL 6.5 on z/VM 6.2 using the latest edition of > Michael MacIsaac's "Virtualization Cookbook", which is written around z/VM > 6.3 and RHEL 6.4. > > We "cloned" a new Linux guest from our RHEL 6.5 "golden image", and one of > our Linux admins noticed some "strange" messages in the clone's boot log: > > = Begin paste = > part of the golden image configuration included a section on settings at > boot time - see section 9.2.6 of the pdf. > in looking at the boot log for ch2lqvpsx I see the following messages > HCPDTV040E Device 0190 does not exist > Error: non-zero CP response for command 'DET 190': #40 > HCPDTV040E Device 0191 does not exist > Error: non-zero CP response for command 'DET 191': #40 > HCPDTV040E Device 019D does not exist > Error: non-zero CP response for command 'DET 19D': #40 > HCPDTV040E Device 019E does not exist > Error: non-zero CP response for command 'DET 19E': #40 > = End paste = > > The concern is over the HCPDTV040E messages for the MDISKs used at CMS > logon time. > > The cited section of the "Cookbook" states: > > = Begin paste = > In order for z/VM 6.3 to relocate guests between single system image (SSI) > members, there > must not be any links to CMS disks. The LNXDFLT PROFILE creates links to > minidisks and > assigns virtual device numbers 190, 191, 19D, and 19E. These addresses > must be detached. > The vmcp module is used to accomplish this. > > To do these two tasks, edit the /etc/rc.d/rc.local file, which is run at > boot time: > > # cd /etc/rc.d > # vi rc.local > > And add the following lines: > > #!/bin/sh > # > # This script will be executed *after* all the other init scripts. > # You can put your own initialization stuff in here if you don't > # want to do the full Sys V style init stuff. > > touch /var/lock/subsys/local > chshut halt vmcmd logoff > chshut poff vmcmd logoff > modprobe vmcp > vmcp det 190 > vmcp det 191 > vmcp det 19d > vmcp det 19e > > The z/VM virtual machine should now be logged off when you halt or power > off Linux. > = End paste = > > The appearance of the HCPDVT040E messages seems to suggest that the CMS > disks are already detached when the rc.local script issues the vmcp det xxx > commands. If true, can anybody say when (and by whom or what process) > those disks are detached, apparently before rc.local runs? Is that "new" > for RHEL 6.5? > > TIA, > > -jc- > > ** > Information contained in this e-mail message and in any attachments > thereto is confidential. If you are not the intended recipient, please > destroy this message, delete any copies held on your systems, notify the > sender immediately, and refrain from using or disclosing all or any part of > its content to any other person. > > -- > 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/
RHEL 6.5 "golden image" configuration
Hi, All, We recently installed RHEL 6.5 on z/VM 6.2 using the latest edition of Michael MacIsaac's "Virtualization Cookbook", which is written around z/VM 6.3 and RHEL 6.4. We "cloned" a new Linux guest from our RHEL 6.5 "golden image", and one of our Linux admins noticed some "strange" messages in the clone's boot log: = Begin paste = part of the golden image configuration included a section on settings at boot time - see section 9.2.6 of the pdf. in looking at the boot log for ch2lqvpsx I see the following messages HCPDTV040E Device 0190 does not exist Error: non-zero CP response for command 'DET 190': #40 HCPDTV040E Device 0191 does not exist Error: non-zero CP response for command 'DET 191': #40 HCPDTV040E Device 019D does not exist Error: non-zero CP response for command 'DET 19D': #40 HCPDTV040E Device 019E does not exist Error: non-zero CP response for command 'DET 19E': #40 = End paste = The concern is over the HCPDTV040E messages for the MDISKs used at CMS logon time. The cited section of the "Cookbook" states: = Begin paste = In order for z/VM 6.3 to relocate guests between single system image (SSI) members, there must not be any links to CMS disks. The LNXDFLT PROFILE creates links to minidisks and assigns virtual device numbers 190, 191, 19D, and 19E. These addresses must be detached. The vmcp module is used to accomplish this. To do these two tasks, edit the /etc/rc.d/rc.local file, which is run at boot time: # cd /etc/rc.d # vi rc.local And add the following lines: #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local chshut halt vmcmd logoff chshut poff vmcmd logoff modprobe vmcp vmcp det 190 vmcp det 191 vmcp det 19d vmcp det 19e The z/VM virtual machine should now be logged off when you halt or power off Linux. = End paste = The appearance of the HCPDVT040E messages seems to suggest that the CMS disks are already detached when the rc.local script issues the vmcp det xxx commands. If true, can anybody say when (and by whom or what process) those disks are detached, apparently before rc.local runs? Is that "new" for RHEL 6.5? TIA, -jc- ** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. -- 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: NFS migration
Dns should work just fine... Just google for it... I think root= is the correct syntax... Server should be where you mount the nfs... Offer On Jun 9, 2014 7:03 PM, "Jake anderson" wrote: > Hi, > > Yes this is a netapp exporting the nfs. Could you please provide me whole > syntax ? we gave the DNS instead of serverip. Are there any difference ? > > > On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch > wrote: > > > Is this a netapp exporting the nfs? > > If so you need the root= export option? > > If this is linux then you need the no_root_squash option... > > > > Offer Baruch > > On Jun 9, 2014 6:27 PM, "Jake anderson" > wrote: > > > > > Hi, > > > > > > We again exported the path as anon=0,unmounted and mounted, but still > the > > > root level of user is unable to change the Ownership. > > > > > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie > > > wrote: > > > > > > > Jake anderson writes: > > > > > Recently we did a migration from one NFS storage server to another > > NFS > > > > > storage server. During this Migration all the copied File had > owners > > as > > > > > root. In the recent NFS storage server the FTP server option is no > > more > > > > > available so we have mounted the NFS storage to a linux running on > > > VMware > > > > > infra(as a ftp server). So when we try change the owner of any file > > > > > mounted to Linux we get a permission denied(Even when we try it as > > > root). > > > > > The message we get is "permission denied"(This is the only > message). > > > The > > > > ls > > > > > -l clearly gives that all the file has the owner as root. > > > > > > > > > > Has any undergone this situation ? Why a root cannot change the > > > > owner(root) > > > > > to someother ID ? > > > > > Since the files have the User and Group copied from previous NFS > > > storage. > > > > > Aren't there anyways to change the Owner and Group from Linux ? > > > > > > > > It's the NFS server that's forbidding it. It's very common in all > > > > but the snazziest of NFS environments for the NFS server to "squash" > > > > the root user of NFS clients and treat it as an unprivileged, > > > > anonymous user. This avoids having a root user on any NFS client > > > > getting root-level access to all exported files on the server. > > > > > > > > For a Linux-based NFS server, the export options "root_squash" > > > > (which is the default) and "all_squash" (probably not the case here) > > > > do this. You need an explicit export option "no_root_squash" to allow > > > > root on the chosen NFS clients to be allowed to chown and access > > > > exported files as though they were uid 0 on the server. Other NFS > > > > servers or appliances may present the option differently. > > > > > > > > --Malcolm > > > > > > > > -- > > > > Malcolm Beattie > > > > Linux and System z Technical Consultant > > > > IBM UK Systems and Technology Group > > > > > > > > > -- > > > > 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/ > -- 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: NFS migration
On Mon, Jun 09, 2014 at 09:31:48PM +0530, Jake anderson wrote: > Date: Mon, 9 Jun 2014 21:31:48 +0530 > Hi, > Yes this is a netapp exporting the nfs. Could you please provide me whole > syntax ? we gave the DNS instead of serverip. Are there any difference ? > # on the NetAPP see "exports" # try `man 5 exports` /vol/pathto/export/qtree-sec=sys,rw=9.9.9.0/24,root=9.9.9.0/24 # exports anything in the /vol/pathto/export/qtree directory on the NetAPP to any Box in 9.9.9.0/24 # note that Client-Boxen in 9.9.9.0/32 will be allowed root-access to the "correct" UID/GIDs # I don't recommend having your stotage-net routable, the NetApp admin interface belongs in the admin vlan. # note that the pseudo-net "9.9.9.9" should be spoken in German "nein.nein.nein.nein" # be create & use your own. # ASSuME that the exporting server is at 9.9.9.1 # on the cleint side (importing) - see /etc/fstab # `man 5 fstab` 9.9.9.1:/vol/pathto/export/qtree/media/nfs/nein-nein-nein nfs rw,bg,nolock,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,timeo=600 0 0 # people will argue about parameters all day - these work for me # DNS | IP - your choice of burocracies. # DNS works if you want your SAN Network visible throughout your DNS (I don't) # IP works if you're prepared to look after changes (etc/hosts, /etc/fstab) when new storages come or go. //rhi -- ... Point and click ... ... probably means that you forgot to load the gun ... Have a nice day ;-) Richard Higson mailto:richard.hig...@gt.owl.de -- 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: NFS migration
Hi Alan, Thanks. I was wondering why anon=0 didnt worked. On 9 Jun 2014 21:44, "Alan Altmark" wrote: > On Monday, 06/09/2014 at 12:03 EDT, Jake anderson > wrote: > > > Yes this is a netapp exporting the nfs. Could you please provide me > whole > > syntax ? we gave the DNS instead of serverip. Are there any difference ? > > Jake, you can google "netapp uid 0" and find full syntax and more > discussion at > > http://seriousbirder.com/blogs/netapp-nfs-permission-denied-errors-for-root/ > > Alan Altmark > > Senior Managing z/VM and Linux Consultant > IBM System Lab Services and Training > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > alan_altm...@us.ibm.com > IBM Endicott > > -- > 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: NFS migration
On Monday, 06/09/2014 at 12:03 EDT, Jake anderson wrote: > Yes this is a netapp exporting the nfs. Could you please provide me whole > syntax ? we gave the DNS instead of serverip. Are there any difference ? Jake, you can google "netapp uid 0" and find full syntax and more discussion at http://seriousbirder.com/blogs/netapp-nfs-permission-denied-errors-for-root/ Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- 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: NFS migration
Hi, Yes this is a netapp exporting the nfs. Could you please provide me whole syntax ? we gave the DNS instead of serverip. Are there any difference ? On Mon, Jun 9, 2014 at 9:27 PM, Offer Baruch wrote: > Is this a netapp exporting the nfs? > If so you need the root= export option? > If this is linux then you need the no_root_squash option... > > Offer Baruch > On Jun 9, 2014 6:27 PM, "Jake anderson" wrote: > > > Hi, > > > > We again exported the path as anon=0,unmounted and mounted, but still the > > root level of user is unable to change the Ownership. > > > > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie > > wrote: > > > > > Jake anderson writes: > > > > Recently we did a migration from one NFS storage server to another > NFS > > > > storage server. During this Migration all the copied File had owners > as > > > > root. In the recent NFS storage server the FTP server option is no > more > > > > available so we have mounted the NFS storage to a linux running on > > VMware > > > > infra(as a ftp server). So when we try change the owner of any file > > > > mounted to Linux we get a permission denied(Even when we try it as > > root). > > > > The message we get is "permission denied"(This is the only message). > > The > > > ls > > > > -l clearly gives that all the file has the owner as root. > > > > > > > > Has any undergone this situation ? Why a root cannot change the > > > owner(root) > > > > to someother ID ? > > > > Since the files have the User and Group copied from previous NFS > > storage. > > > > Aren't there anyways to change the Owner and Group from Linux ? > > > > > > It's the NFS server that's forbidding it. It's very common in all > > > but the snazziest of NFS environments for the NFS server to "squash" > > > the root user of NFS clients and treat it as an unprivileged, > > > anonymous user. This avoids having a root user on any NFS client > > > getting root-level access to all exported files on the server. > > > > > > For a Linux-based NFS server, the export options "root_squash" > > > (which is the default) and "all_squash" (probably not the case here) > > > do this. You need an explicit export option "no_root_squash" to allow > > > root on the chosen NFS clients to be allowed to chown and access > > > exported files as though they were uid 0 on the server. Other NFS > > > servers or appliances may present the option differently. > > > > > > --Malcolm > > > > > > -- > > > Malcolm Beattie > > > Linux and System z Technical Consultant > > > IBM UK Systems and Technology Group > > > > > > -- > > > 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: NFS migration
Is this a netapp exporting the nfs? If so you need the root= export option? If this is linux then you need the no_root_squash option... Offer Baruch On Jun 9, 2014 6:27 PM, "Jake anderson" wrote: > Hi, > > We again exported the path as anon=0,unmounted and mounted, but still the > root level of user is unable to change the Ownership. > > > On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie > wrote: > > > Jake anderson writes: > > > Recently we did a migration from one NFS storage server to another NFS > > > storage server. During this Migration all the copied File had owners as > > > root. In the recent NFS storage server the FTP server option is no more > > > available so we have mounted the NFS storage to a linux running on > VMware > > > infra(as a ftp server). So when we try change the owner of any file > > > mounted to Linux we get a permission denied(Even when we try it as > root). > > > The message we get is "permission denied"(This is the only message). > The > > ls > > > -l clearly gives that all the file has the owner as root. > > > > > > Has any undergone this situation ? Why a root cannot change the > > owner(root) > > > to someother ID ? > > > Since the files have the User and Group copied from previous NFS > storage. > > > Aren't there anyways to change the Owner and Group from Linux ? > > > > It's the NFS server that's forbidding it. It's very common in all > > but the snazziest of NFS environments for the NFS server to "squash" > > the root user of NFS clients and treat it as an unprivileged, > > anonymous user. This avoids having a root user on any NFS client > > getting root-level access to all exported files on the server. > > > > For a Linux-based NFS server, the export options "root_squash" > > (which is the default) and "all_squash" (probably not the case here) > > do this. You need an explicit export option "no_root_squash" to allow > > root on the chosen NFS clients to be allowed to chown and access > > exported files as though they were uid 0 on the server. Other NFS > > servers or appliances may present the option differently. > > > > --Malcolm > > > > -- > > Malcolm Beattie > > Linux and System z Technical Consultant > > IBM UK Systems and Technology Group > > > > -- > > 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: NFS migration
Hi, We again exported the path as anon=0,unmounted and mounted, but still the root level of user is unable to change the Ownership. On Mon, Jun 9, 2014 at 4:47 PM, Malcolm Beattie wrote: > Jake anderson writes: > > Recently we did a migration from one NFS storage server to another NFS > > storage server. During this Migration all the copied File had owners as > > root. In the recent NFS storage server the FTP server option is no more > > available so we have mounted the NFS storage to a linux running on VMware > > infra(as a ftp server). So when we try change the owner of any file > > mounted to Linux we get a permission denied(Even when we try it as root). > > The message we get is "permission denied"(This is the only message). The > ls > > -l clearly gives that all the file has the owner as root. > > > > Has any undergone this situation ? Why a root cannot change the > owner(root) > > to someother ID ? > > Since the files have the User and Group copied from previous NFS storage. > > Aren't there anyways to change the Owner and Group from Linux ? > > It's the NFS server that's forbidding it. It's very common in all > but the snazziest of NFS environments for the NFS server to "squash" > the root user of NFS clients and treat it as an unprivileged, > anonymous user. This avoids having a root user on any NFS client > getting root-level access to all exported files on the server. > > For a Linux-based NFS server, the export options "root_squash" > (which is the default) and "all_squash" (probably not the case here) > do this. You need an explicit export option "no_root_squash" to allow > root on the chosen NFS clients to be allowed to chown and access > exported files as though they were uid 0 on the server. Other NFS > servers or appliances may present the option differently. > > --Malcolm > > -- > Malcolm Beattie > Linux and System z Technical Consultant > IBM UK Systems and Technology Group > > -- > 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: NFS migration
Jake anderson writes: > Recently we did a migration from one NFS storage server to another NFS > storage server. During this Migration all the copied File had owners as > root. In the recent NFS storage server the FTP server option is no more > available so we have mounted the NFS storage to a linux running on VMware > infra(as a ftp server). So when we try change the owner of any file > mounted to Linux we get a permission denied(Even when we try it as root). > The message we get is "permission denied"(This is the only message). The ls > -l clearly gives that all the file has the owner as root. > > Has any undergone this situation ? Why a root cannot change the owner(root) > to someother ID ? > Since the files have the User and Group copied from previous NFS storage. > Aren't there anyways to change the Owner and Group from Linux ? It's the NFS server that's forbidding it. It's very common in all but the snazziest of NFS environments for the NFS server to "squash" the root user of NFS clients and treat it as an unprivileged, anonymous user. This avoids having a root user on any NFS client getting root-level access to all exported files on the server. For a Linux-based NFS server, the export options "root_squash" (which is the default) and "all_squash" (probably not the case here) do this. You need an explicit export option "no_root_squash" to allow root on the chosen NFS clients to be allowed to chown and access exported files as though they were uid 0 on the server. Other NFS servers or appliances may present the option differently. --Malcolm -- Malcolm Beattie Linux and System z Technical Consultant IBM UK Systems and Technology Group -- 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/
2014 VM Workshop attendee registration remains open, final deadline for remaining FREE STUFF draws near: 23:59 this Wednesday, June 11.
The 2014 VM Workshop, June 26-28 2014 will be conducted at North Carolina A&T
State University, Greensboro NC
The "Early Registration" deadline for guaranteed delivery of a free 2014 VM
Workshop polo shirt (for regular attendees), T-shirt (for student attendees),
and to order dorm room lodging, passed at 23:59 Friday May 30.
You have one more chance to register before the final deadline for FREE STUFF
passes at 23:59 PM this Wednesday, June 11. The remaining FREE STUFF is
limited to two items:
1) admittance to the Thursday Evening Gala Reception and Banquet Dinner,
and
2) an 'Aggie' debit card pre-loaded with $65 for food purchases in the
campus cafeteria.
Due to university ordering deadlines, any attendee registering after that time
will probably not be able to receive either of these at the workshop.
WHO:
z/VM, and Linux on System z Friends
WHAT:
Location, travel, nearby hotels, travel hints, sponsor information, and
registration details for the 2014 VM Workshop have all been posted to:
http://www.vmworkshop.org/2014
Session agenda information will be available later this week.
WHERE:
North Carolina A&T State University, Greensboro NC
WHEN:
SESSION DATES: From Thursday morning JUNE 26 until about 1PM EDT, Saturday JUNE
28.
Choose from multiple concurrent presentations packed full of up-to-the-minute
technical sessions for all expertise levels of z/VM, and Linux on System z, and
from Hands-On Labs including:
- z/VM 6.3.0 Installation or Migration (your choice),
-'Linux on System z' Installation (SLES or Redhat, your choice),
- Intro to REXX
Wednesday June 25 is reserved for VM Workshop Volunteer Committee site
preparation and lab setup, if you are interested in joining just send me an
e-mail off-list asking to join.
WHY:
Previous VM Workshops have been referred to by the small-minded as: 'a large
number of system programmers with some limited adult supervision' (do you
really want to miss this!??). Expect another wonderful "up close and personal"
workshop with great content and terrific camaraderie. Come to meet VM
old-timers... and *future* z/VM old-timers while learning the latest technical
z/VM and 'Linux on System z' details. Don't know where to start with Linux on
System z? This is a great place to start!
PRICE:
STILL UNCHANGED from the previous three years, ** ONLY $100 per attendee**.
This is the best bargain out there for z/VM and 'Linux on System z' education,
and is quite reasonable for anyone paying their own way. Parking is available
on-site for $6 per day.
Regular attendees and sponsor attendees: The $100 registration fee for regular
attendees includes: access to all sessions and hands-on labs, if registration
is completed before 23:59 PM Wednesday June 11: a Gala Reception and Banquet
Dinner on Thursday evening, and... an NC A&T "Aggie" debit card loaded with $65
to purchase other meals and snacks on campus.
Full-time Students: A $10 registration fee includes: access to all sessions and
hands-on labs, and optional, same deadline attendance at the Gala Dinner
Reception on Thursday evening.
Spouse attendees: A $0 registration fee provides: an optional means to purchase
attendance at the Gala Reception and Banquet Dinner on Thursday evening ($20).
HOW:
Registration is now LIVE, please check it out soon! (Live servers are
standing by to take your registration!)
Advice: onsite registration is not likely, and will involve additional fees to
the university and thus... to you, so register now!
PARTICIPATE:
Compete in the historical (occasionally hysterical) VM Workshop "Ugly Hawaiian
Shirt" contest for a chance to win a treasured, but ugly prize! (B.Y.O.U.H.S.)
Place this event on your calendars and please join us at North Carolina A&T
State University. Don't miss this incredibly inexpensive, educational, and fun
event!
The VM Workshop is sponsoring a 12 question survey to help us all better
understand the current state of our platform within the organizations we
support. The results will help us highlight successes and focus our
conversations and collective resources to address the major challenges the
community faces. This is a survey of the community, for the community. Those
who respond will receive a summary of the results via email.
The more responses, the better the data! Please take a few minutes to respond
at: https://www.research.net/s/vmcommunity
This e-mail was sent on behalf of the 2014 VM Workshop Volunteer Committee.
Mike Walter
Mike Walter (at) Aon {dot} com
Work: 847.883.7822
--
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
---
NFS migration
Hello, Cross Mounted Recently we did a migration from one NFS storage server to another NFS storage server. During this Migration all the copied File had owners as root. In the recent NFS storage server the FTP server option is no more available so we have mounted the NFS storage to a linux running on VMware infra(as a ftp server). So when we try change the owner of any file mounted to Linux we get a permission denied(Even when we try it as root). The message we get is "permission denied"(This is the only message). The ls -l clearly gives that all the file has the owner as root. Has any undergone this situation ? Why a root cannot change the owner(root) to someother ID ? Since the files have the User and Group copied from previous NFS storage. Aren't there anyways to change the Owner and Group from Linux ? Any suggestions would be appreciated. Jake -- 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/
