You need to log in to create posts and topics. Login · Register
Nfs exports preserve user files ownership,existing uid and gid
rahulraj
15 Posts
April 15, 2024, 5:53 pm
Quote from rahulraj on April 15, 2024, 5:53 pm
could you send a user's files into the petasan nfs exports with their existing uid and gid.If it is possible how it will configure in my Nfs exports.
could you send a user's files into the petasan nfs exports with their existing uid and gid.If it is possible how it will configure in my Nfs exports.
admin
2,858 Posts
April 15, 2024, 9:29 pm
Quote from admin on April 15, 2024, 9:29 pm
NFS 4 supports kerberos type security with domain groups and user permissions. It is not currently supported in PetaSAN, we may support it but not in near future. It is also not very common. PetaSAN supports the more common restrictions based on client ip addresses.
NFS 4 supports kerberos type security with domain groups and user permissions. It is not currently supported in PetaSAN, we may support it but not in near future. It is also not very common. PetaSAN supports the more common restrictions based on client ip addresses.
rahulraj
15 Posts
April 18, 2024, 2:10 am
Quote from rahulraj on April 18, 2024, 2:10 am
While copying files from another linux server to my petasan nfs export, that time how to preserve files's uid&gid(ownership) at the destination location(Nfs export).
While copying files from another linux server to my petasan nfs export, that time how to preserve files's uid&gid(ownership) at the destination location(Nfs export).
admin
2,858 Posts
April 18, 2024, 11:26 am
Quote from admin on April 18, 2024, 11:26 am
As per earlier this needs kerberos to provide domain wide user authentication and authorisation. Without it, you will have a uid of example 1003 on host client1 represent a totally different user than uid of 1003 on host client2 and different user on PetaSAN nodes, it will not be possible to authenticate user (validate user with password), or authorise (grant file access based on permissions).
As per earlier this needs kerberos to provide domain wide user authentication and authorisation. Without it, you will have a uid of example 1003 on host client1 represent a totally different user than uid of 1003 on host client2 and different user on PetaSAN nodes, it will not be possible to authenticate user (validate user with password), or authorise (grant file access based on permissions).
