Sponsored Content
Full Discussion: Chgrp failed on NAS mounted
Operating Systems Solaris Chgrp failed on NAS mounted Post 302894911 by achenle on Thursday 27th of March 2014 11:11:18 PM
Old 03-28-2014
A NAS server may not know the groups a user belongs to. If _POSIX_CHOWN_RESTRICTED is enforced by the NAS server, and it doesn't have access to the group data, it won't allow the change if it's not aware of the group(s) the file owner belongs to.

Although I had thought the group data was part of the NFS protocol? That may have changed in NFSv4, as I can see how trusting a client to supply gids could potentially be a security issue. I know my the first thing I do when I have any problem at all with NFSv4 is try NFSv3. Especially in a heterogeneous environment where various OS breeds and flavors are sharing NFS mounts. (Yeah, I avoid NFSv4 whenever possible.)

Being shared R/W to everyone shouldn't matter.
 

9 More Discussions You Might Find Interesting

1. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ... (4 Replies)
Discussion started by: brizrobbo
4 Replies

2. UNIX for Dummies Questions & Answers

Chgrp and Chown ???

Hi Can anybody please let me know the usage of Chgrp command with an example??? Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies

3. OS X (Apple)

AFP mount + Chown/Chgrp respecting

Hello all... Does anyone know how to make an AFP mount of home directories (/Volumes/users off of another server) so that any users doing an ssh login retain write permission to their individual folders, read-write permissions to folders chowned to appropriate group... and so that newly created... (0 Replies)
Discussion started by: drkdev
0 Replies

4. Shell Programming and Scripting

Can't chgrp, chown on Linux

I have a problem on Linux wherein it doesn't allow me to use the chown and chgrp even if I am the owner of the file. Is this one of the Linux limitations? BTW, I can use chmod. (4 Replies)
Discussion started by: Jin_
4 Replies

5. Shell Programming and Scripting

Check if NAS filesystem is mounted

Anyone know the best way to check and see if a NAS filesystem is mounted on a linux box. I have no idea where to start :wall:. (2 Replies)
Discussion started by: d3mon_spawn
2 Replies

6. Solaris

how to make nas share mounted in zones persistent across reboots?

there are few nas shares that would be mounted on the local zone. should i add an entry into the add an entry in zone.xml file so that it gets mounted automatically when the zone gets rebooted? or whats the correct way to get it mounted automatically when the zone reboots (2 Replies)
Discussion started by: chidori
2 Replies

7. Red Hat

Can't chgrp. Error - chgrp: changing group of `<file>': Invalid argument

I found that I cannot chgrp for some reason with error: chgrp: changing group of `<file>': Invalid argument This happens on all NFS mounted disks on client machines. We use AD (not my call) for authentication and it also provides groups. We have a NFS server running Scientific Linux 6.3... (1 Reply)
Discussion started by: venmx
1 Replies

8. UNIX for Dummies Questions & Answers

Extremely slow file writing with many small files on mounted NAS

I am working on a CentOS release 6.4 server which has two mounted NAS devices, one with 20 x 3TB HDD running in FreeBSD with Zfs2 and one NAS which I don't know much about, but which has 7 HDDs in RAID-6. I was running tar -zxvf on a tarball that is 80Mb with 50,000 small files inside. Even... (4 Replies)
Discussion started by: TupTupBoom
4 Replies

9. Red Hat

Related to "NAS" some file system (mounted volumes) were not writable

Dear friends, I have been facing an issue with one of my red hat unix machine, suddenly lost to switch sudo users. My all colleagues lost to switch to access sudo users. Then, we have realized its related to NAS issue which does not allowing to write the file. because of this we got so many... (1 Reply)
Discussion started by: Chand
1 Replies
scnas(1M)						  System Administration Commands						 scnas(1M)

NAME
scnas - manage network-attached storage (NAS) device configuration data for Sun Cluster. SYNOPSIS
scnas [-H] scnas -a [-H] [-n] -h device-name -t device-type -o specific-options [-f input-file] scnas -c [-H] [-n ] -h device-name -o specific-options [-f input-file] scnas -p [-H] [-h device-name] [-t device-type] scnas -r [-H ] -h device-name DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The scnas command manages NAS devices in a Sun Cluster configuration. To manage NAS directories in the cluster, use the scnasdir command. You can use the scnas command to create the NAS device configuration, to update the NAS type-specific properties, and to remove the device configuration from Sun Cluster. The options to this command are processed in the order in which they are typed on the command line. The scnas command can only be run from an active cluster node. The results of running the command are always the same, regardless of the nodethat is used. All forms of the scnas command accept the -H option. Specifying -H displays help information. All other options are ignored. Help informa- tion is also printed when scnas is run without options. The NAS device must be set up before using the scnas command to manage a NAS device. Refer to the documentation for the particular NAS device for procedures for setting up a device. You can use this command only in the global zone. OPTIONS
Basic Options The following options are common to all forms of the scnas command: -H If this option is specified on the command line at any position, the command prints help information. All other options are ignored and are not executed. Help information is also printed if scnas is run with no options. You can use this option only in the global zone. -n If this option is specified on the command line at any position, the scnas command only checks the usage and does not write the config- uration data. If the -n option is specified with the -f option, the scnas command checks the input file for the password. The following options modify the basic form and function of the scnas command. None of these options can be combined on the same command line. -a Specifies the add form of the scnas command. You can use this option only in the global zone. The -a option can be used to add a NAS device into the Sun Cluster configuration. Depending on the type of your NAS device, you might have to set additional properties. These required properties are also explained in the -t option description in the "Additional Options" section. -c Specifies the change form of the scnas command. The -c option is used to change specific NAS device properties. You can use this option only in the global zone. -r Specifies the remove form of the scnas command. The -r option is used to remove the NAS device from the Sun Cluster configuration. You can use this option only in the global zone. Before removing a device, all its exported directories must be removed by using scnasdir. -p Specifies the print form of the scnas command. You can use this option only in the global zone. When no other options are given, the -p option prints a listing of all the current NAS devices configured in Sun Cluster and all their associated properties. This option can be used with additional options to query a particular device or a particular type of device. Additional Options The following additional options can be combined with one or more of the previously described basic options to configure all properties for a device. The device does not need to be online to use these options. Refer to the SYNOPSIS section to see the options that can be used with each form of scnas. The additional options are as follows: -h device-name Use this option to specify the name of the NAS device in the Sun Cluster configuration. The device name identifies the device and can be used to remotely access the device by using rhs or telnet. This device name must be specified for the add, change, and remove forms of the scnas command. -t device-type The NAS device type. You must specify this option when you add a NAS device to the Sun Cluster configuration. The NAS device type is identified by the vendor name. You can specify either sun for a NAS device from Sun Microsystems, Inc. or netapp for a NAS device from Network Appliance, Inc. Different types of NAS devices have different or in some cases, no properties. -o specific-options Use this option to provide the properties that are specific to a NAS device type. For example, the NAS device from Network Appliance, Inc. has the following property: -o userid=userid Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. The userid property is used by the cluster to perform administrative duties on the device. When you add a userid to the device configu- ration, you are prompted for its password. You can also place the password in a text file and use it by specifying the -f option. -finput-file For security reasons, the password cannot be specified in command-line options. To keep the password secure, place it in a text file and specify the file by using the -f option. If you do not specify an input file for the password, the command prompts for the pass- word. Note - You do not specify properties for the NAS device from Sun Microsystems, Inc. As this device does not have any properties, the -f and -o options do not apply. Set permissions of the input file to readable by root and prohibit access by either group or world. In the input file, the password cannot be entered across multiple lines. Leading white spaces and tabs are ignored. Comments begin with an unquoted pound (#) sign, and continue to the next new line. The parser ignores all comments. When you use an input file for the device user password, the # sign cannot be part of the password. EXAMPLES
Example 1 Adding a NAS Device From Sun Microsystems, Inc. to a Cluster The following scnas command adds a Sun Microsystems, Inc. storage system to the Sun Cluster configuration. # scnas -a -h sunnas1 -t sun Example 2 Adding a NAS Device From Network Appliance, Inc. to a Cluster The following scnas command adds a Network Appliance, Inc. storage system to the Sun Cluster configuration. # scnas -a -h netapp1 -t netapp -o userid=root Please enter password: Example 3 Removing a NAS Device From a Cluster The following scnas command removes a NAS device from the Sun Cluster configuration. # scnas -r -h sunnas1 EXIT STATUS
The following exit values are returned: 0 The command executed successfully. nonzero An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), clnasdevice(1CL), clquorum(1CL), cluster(1CL), scconf(1M), scnasdir(1M) Sun Cluster 3.2 6 Sep 2007 scnas(1M)
All times are GMT -4. The time now is 10:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy