Reply
Byte
macgyver7002
Posts: 6
Registered: ‎06-23-2009
0

Black Armor 420 NAS NFS file/directory ownership and permissions

I am copying my network files to my new Blackarmor NAS 420 from my linux server using NFS.  I find the default permissions way too restrictive, and am unable to change the permissions, or ownership from nobody:nogroup.  Is it possible to use my existing users and groups (eg user:users).  I have set up the NFS share with public access enabled (and disabled) and set NFS Access to Full Access.  Am I missing something?
Former Seagate Employee
ChrisS
Posts: 84
Registered: ‎11-11-2007
0

Re: Black Armor 420 NAS NFS file/directory ownership and permissions

Hi,

 

The BA uses the nfs server option of "all_squash" to map all user/groups to the "nobody" (uid/gid = 65534) user. So you won't be able to change ownership. I believe that you should be able to change permissions.

 

Are you getting any errors adding or deleting files?

When are you running into problems? Can you describe the what you are doing so I can try and reproduce it?

 

-c

 

Byte
macgyver7002
Posts: 6
Registered: ‎06-23-2009
0

Re: Black Armor 420 NAS NFS file/directory ownership and permissions

Hi Chris

 

I want to have better control over my permissions on the NAS box.  I am currently unable to join my domain (Windows 2008 server) (I get the [Join ADS Failed error]), so I was hoping I'd be able to achieve those results through NFS.  I'm quickly coming to the conclusion that purchasing this box was a bit of a mistake.  If you can help solve either issue, I would be eternally grateful. haha.

 

The reason I wanted to change ownership is so I can host my linux home directories on the NAS box.  If I'm able to finally join the domain, that would be acceptable too.

 

On the AD side of things, I have both the Administrator account, and mine as part of the Domain Admins, and the Enterprise Admins.  I have also delegated the ability to add computers to the domain to both accounts.  I can ping the NAS box and access it from my domain controller, and it shows up correctly when I run nslookup.  Is there a way I can ssh into the box and try to get a little more information on what the problem is?

 

 I would like to get this resolved as soon as possible, as it is beginning to take up too much of my time.

 

Thanks

Byte
macgyver7002
Posts: 6
Registered: ‎06-23-2009
0

Re: Black Armor 420 NAS NFS file/directory ownership and permissions

I guess I should mention that if I use

 

netdom join <nas server name> /domain:<domain name> /verbose

 

I get these results:

 

Joining domain mkcnetwork.mkc.com

The computer rename attempt failed with error 1728.

A remote procedure call (RPC) protocol error occurred.

The command failed to complete successfully.

Visitor
randomsense
Posts: 1
Registered: ‎07-30-2009
0

Re: Black Armor 420 NAS NFS file/directory ownership and permissions

I'm having the same problem. Is there anyway to make it use no_root_squash or something similar?

 

I'm trying to use the NAS to host files for a linux server application that unfortunatly requires a specific user/group for these files. Without this I'm stuck and the app wont run.