I have inherited configuration of a 740. I struggled for hours trying to install Ontap via CIFs and threw up my hands because I could not map the root volume. So, I tried NFS and did get it to mount and even got the new OS to copy over to the filer. The problem is I cannot change the permissions of any of the files nor change their owner. I _can_ create/edit files. This was particularly irritating when the install script untarred all of the OS files to the filer and the screen filled with "Operation not permitted" messages. Anyone overcome this problem before? Thanks.
Note: UNIX style permissions CIFS is disabled (for the moment). NetApp Release 6.1.1R2 NFS client is Linux
-John
Unable to chown/chmod filesI had a problem like this once or twice (not completely solved). I overcome the problem in modifying the /etc/passwd file. The problem seems to be related to the different way the root is defined beetween Linux and Unix : unix : root GID is 1 linux : root GID is 0 ! tray to reinstall the soft from a Unix machine or modify the /etc/passwd file to turn GID to the corresponding GID. Thank you to let us know if it works : )
----- Original Message ----- From: John Coke To: 'toasters@mathworks.com' Sent: Thursday, December 06, 2001 5:17 AM Subject: Unable to chown/chmod files
I have inherited configuration of a 740. I struggled for hours trying to install Ontap via CIFs and threw up my hands because I could not map the root volume. So, I tried NFS and did get it to mount and even got the new OS to copy over to the filer. The problem is I cannot change the permissions of any of the files nor change their owner. I _can_ create/edit files. This was particularly irritating when the install script untarred all of the OS files to the filer and the screen filled with "Operation not permitted" messages. Anyone overcome this problem before? Thanks.
Note: UNIX style permissions CIFS is disabled (for the moment). NetApp Release 6.1.1R2 NFS client is Linux
-John
The problem seems to be related to the different way the root is defined beetween Linux and Unix : unix : root GID is 1 linux : root GID is 0
Actually, there exist flavors of UNIX that use 0 as the root group:
hostname$ uname -sr SunOS 5.8 hostname$ egrep '^root' /etc/group root::0:root
hostname2$ uname -sr HP-UX B.11.00 hostname2$ egrep '^root' /etc/group root::0:root
and the root UID is 0 on all flavors of UNIX I know of.
I suspect the more likely explanation is that the person who sent the original mail might not have had the filer exporting the file system in question with root permission to the client he was using, as somebody suggested in another mail message.
guy@netapp.com (Guy Harris) writes:
The problem seems to be related to the different way the root is defined beetween Linux and Unix : unix : root GID is 1 linux : root GID is 0
Actually, there exist flavors of UNIX that use 0 as the root group:
hostname$ uname -sr SunOS 5.8 hostname$ egrep '^root' /etc/group root::0:root
hostname2$ uname -sr HP-UX B.11.00 hostname2$ egrep '^root' /etc/group root::0:root
and the root UID is 0 on all flavors of UNIX I know of.
I think there's some confusion about what what was meant by "the root group" here. Certainly in Solaris 2+ the group with gid 0 is named "root" (unlike systems with a BSD flavour where it is usually called "wheel"). But the login group for root is not that one but the one with gid 1:
$ uname -sr SunOS 5.8 $ egrep ^root /etc/passwd root:x:0:1:Super-User:/:/sbin/sh $ egrep :1: /etc/group other::1:
This will usually be the real & effective gid in a session as root, including one initiated by the "su" command. This really is an ancient and common tradition in Unix(-like) systems: L(inux)I(s)N(ot)U(ni)X does seem to be rather the odd one out in having rationalised the login group for root to be gid 0.
But all this is almost certainly beside the point, because I agree with Guy when he says...
I suspect the more likely explanation is that the person who sent the original mail might not have had the filer exporting the file system in question with root permission to the client he was using, as somebody suggested in another mail message.
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QH, Phone: +44 1223 334715 United Kingdom.
John,
The system from which you are trying to work will need root permissions on the root volume. Be sure to check the /etc/exports file to see if the host that you are using is included both in the access and root options of the export. Once your hosts is added to the list, you will need to re-export the file system "exportfs -a" works well.
[9]% cat exports #Auto-generated by setup Mon Jan 11 19:38:12 CST 1999 /vol/vol0 -access=admin1,root=admin1
Also check the /etc/hosts.equiv
[8]% cat hosts.equiv #Auto-generated by setup Thu Nov 15 16:47:41 GMT 2001 admin1
This file will define those files that are allowed to "rsh" to the filer. Personally, I put the administrative host name and IP address in the /etc/hosts file so that the filer does not require DNS to be running in order to find the administrative host names. This is useful after power outages. After such occasions, once our networking group has the network infrastructure operational, i.e. routers and such, I can bring the filers up completely independent of the rest of our infrastructure, such as NIS/NIS+, DNS, etc.
I hope this helps. Please feel free to drop me a line if you need more help. -gdg
John Coke wrote:
I have inherited configuration of a 740. I struggled for hours trying to install Ontap via CIFs and threw up my hands because I could not map the root volume. So, I tried NFS and did get it to mount and even got the new OS to copy over to the filer. The problem is I cannot change the permissions of any of the files nor change their owner. I _can_ create/edit files. This was particularly irritating when the install script untarred all of the OS files to the filer and the screen filled with "Operation not permitted" messages. Anyone overcome this problem before? Thanks.
Note: UNIX style permissions CIFS is disabled (for the moment). NetApp Release 6.1.1R2 NFS client is Linux
-John
-
Chris Thompson -
FPS France -
Guy Harris -
John Coke -
Mr. G. D. Geen