chown -R xyxname:users run from / !!!

[S.N.S]

Yes,

I need to do that -- the Servers had multiple problems when I took over ; so was concentrating on them.

Some basic things to be checked and done.

Thanks again for your inputs,
Appreciate your time.

Will Update on the issue in 2days.

Dunke
SNS

[Benoy Daniel]

try to run a find command and can findout which are the files got modified recently. This may able to help you..

find -ctime

True if the time of last change of file status information subtracted from the initialization time is n-1 to n multiples of 24 h.

[Horia Chirculescu]

Hello,

>other VGs pertain to the SAN - all related to cluster VG, and VGs for Oracle -
in recovery terms - no related application data on the server..

My point was this: if the VGs that contain LUNs from SAN (at SAN level, only LUNs are 'known') were actually mounted on the very same node when your user run the chown command, then the ownership of those files are also modified! So you need to check those files also.

Of course, no harm was done if the volumes were unmounted at that time.

Best regards,
Horia.

[S.N.S]

Hi,

Horia, unfortunately shared VGs are on the same node...

Best to run the script - right?

And yes, Benoy, there are more the 4700 file permissions changed..

Will update you all
Dunke
SNS