Subscribe

directory ownership and SMO

[ Edited ]

I created some new volumes, and qtrees on the filer and the exports got created as well.

I modified the /etc/fstab on the linux host , created the directories, subdirectories, and modified the ownership. In my case it had to be owned by oracle:dba instead of root:root

Everything looks good up until I mount those newly created volumes with their mount points.  Once I mount them (mount -a), the owneship switches to root:root.

Anyone has faced this same issue?  How did you get it resolved?

Re: directory ownership and SMO

What you describe is normal.

You modified the permissions on the directory structure on the client prior to mounting - all you did was set the perms on the mount point.  Volumes/qtrees are created with root:root by default (if using unix permissions, of course), and the acls of the remote filesystem are what show up on the mount point after a mount.

You need to mount everything up, then change the permissions and ownership.  If you then mount the volume on another host, the permissions will already be set.

Hope that helps.

Bill

Re: directory ownership and SMO

Bill,

Thanks for replying.

If I mount everything and then try to change ownership, I get the following:

# chown -R oracle:dba LVTEST LVDEV

chown: changing ownership of `LVTEST/redob/.snapshot': Read-only file system

chown: changing ownership of `LVTEST/exp/.snapshot': Read-only file system

chown: changing ownership of `LVTEST/arch/.snapshot': Read-only file system

chown: changing ownership of `LVTEST/redoa/.snapshot': Read-only file system

chown: changing ownership of `LVTEST/ctrl/.snapshot': Read-only file system

chown: changing ownership of `LVTEST/data/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/redob/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/exp/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/arch/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/redoa/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/ctrl/.snapshot': Read-only file system

chown: changing ownership of `LVDEV/data/.snapshot': Read-only file system

Re: directory ownership and SMO

That should be fine.  You won't be able to modify the .snapshot directories because (like the error says) they are read only.  If you look at the LVTEST and LVDEV directories and sub directories, you should see them with the permissions you specified.  .snapshot will always be root:root:777 I think - but the snapshot content, under .snapshot/<snap_name>/, will mirror the permissions on the live filesystems at the time the snapshot was taken.

Bill

Re: directory ownership and SMO

Great , thank you.... It was throwing me off seeing the output I pasted last.

Thanks again Bill