volume ownership changes at reboot - Veritas Volume Manager

This is a discussion on volume ownership changes at reboot - Veritas Volume Manager ; I have VM 3.2 with the most recent patch running on a Solaris 7 (with the most recent patch cluster) machine. I created several volumes and used vxedit to change the ownership of the volumes to oracle:dba. I then created ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: volume ownership changes at reboot

  1. volume ownership changes at reboot


    I have VM 3.2 with the most recent patch running on a Solaris 7 (with the
    most recent patch cluster) machine. I created several volumes and used vxedit
    to change the ownership of the volumes to oracle:dba. I then created mount
    points and set the ownership of the mount points to oracle:dba using chown.
    When I mount the filesystems on these volumes, the ownership of the mount
    points changes to root and oracle cannot create any files or directories
    on the volumes. I went into VMSA and verified that the ower of the volumes
    is still set as oracle:dba. Any idea why this is happening? I've done this
    many times in the past and never had this problem before.

  2. Re: volume ownership changes at reboot

    Hi Ron,

    The owner and the permissions on the folder to become the mountpoint has no
    effect when the filesystem is mounted. The mounted filesystem will be on top of
    the folder and use its own settings for owner and permissions.
    The first time a filesystem is mounted the ownership is root:root and the
    persmissions are 755. This is the default behavior. When the filesystem is
    mounted you then can change the owner and permissions to suit your needs. It will
    be remembered during a umount / mount cycle. To fix your problem you can either
    do a chmod 777 on the mounted filesystem or do a chown oracle:dba on the mounted
    filesystem, or any combination to suit your needs.

    Hope this helps.

    /Peter


    Ron Bergeron wrote:

    > I have VM 3.2 with the most recent patch running on a Solaris 7 (with the
    > most recent patch cluster) machine. I created several volumes and used vxedit
    > to change the ownership of the volumes to oracle:dba. I then created mount
    > points and set the ownership of the mount points to oracle:dba using chown.
    > When I mount the filesystems on these volumes, the ownership of the mount
    > points changes to root and oracle cannot create any files or directories
    > on the volumes. I went into VMSA and verified that the ower of the volumes
    > is still set as oracle:dba. Any idea why this is happening? I've done this
    > many times in the past and never had this problem before.



+ Reply to Thread