Quote:
Originally Posted by bakunin
The "mount = TRUE" indicates that the FS would be mounted automatically during a reboot, so that rules a reboot out.
The only other way to get a FS into "closed" state is to umount it. Maybe this is done by some script, which runs frequently?
You could write a little script which tests if /home is still mounted in regular intervals and writes a timestamp to a log file each time it is. This way you cound find out when exactly the umount happens. Have a look then in the crontabs, maybe you can find the "offender".
Just guessing, but could it be some that a script mounts an NFS share, tries to umount it and simply gets it wrong - umounting not the NFS share but the /home FS?
I hope this helps.
bakunin
|
Sorry for the late reply guys. Thanks Bak,
Ya your right. Theres a kinda backup script run by tivoli which has umount all and varyoffvg command for some of my apps vgs. But at later after the backup activity theres another script which varyons the same vgs and mounts my application filesystems.
So now the question arises is when the 1st script runs umount all why /home does get in closed/synced mode? though it is system related filesystem?
