05-08-2008
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
4 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
my partner change the server's ip address and now i can't to mount the oracle's filesystem, what i do? i don't want to reinstall Unix. My unix is SCO UNIX 5.0.5 (9 Replies)
Discussion started by: marun
9 Replies
2. Shell Programming and Scripting
Hi
How can I only print the file systems that are more than 95% full.
I used the df -k output and tried to check for each file system and then print only the ones that meet the criteria... But my solution seems cloodgie ... (3 Replies)
Discussion started by: YS2002
3 Replies
3. Solaris
Hi, i have just installed Sun Solaris 8 on the sun sparc server but when i run the browers and write a site to open it my browers automatically closed and when i run the browers window again it again automatically closed again.
can any body help me to resolve this issue (1 Reply)
Discussion started by: adnangc
1 Replies
4. UNIX for Dummies Questions & Answers
Hi Everyone,
Good day.
Scenario:
2 unix servers -- A (SunOS) and B (AIX)
I have an ftp script to sftp 30 files from A to B which happen almost instantaneously i.e 30 sftp's happen at the same time.
Some of these sftp's fail with the following error:
ssh_exchange_identification: Connection... (1 Reply)
Discussion started by: jeevan_fimare
1 Replies
LEARN ABOUT POSIX
umount.nfs
UMOUNT.NFS(8) System Manager's Manual UMOUNT.NFS(8)
NAME
umount.nfs, umount.nfs4 - unmount a Network File System
SYNOPSIS
umount.nfs dir [-fvnrlh ]
DESCRIPTION
umount.nfs and umount.nfs4 are a part of nfs(5) utilities package, which provides NFS client functionality.
umount.nfs4 and umount.nfs are meant to be used by the umount(8) command for unmounting NFS shares. This subcommand, however, can also be
used as a standalone command with limited functionality.
dir is the directory on which the file system is mounted.
OPTIONS
-f Force unmount the file system in case of unreachable NFS system.
-v Be verbose.
-n Do not update /etc/mtab. By default, an entry is created in /etc/mtab for every mounted file system. Use this option to skip delet-
ing an entry.
-r In case unmounting fails, try to mount read-only.
-l Lazy unmount. Detach the file system from the file system hierarchy now, and cleanup all references to the file system as soon as it
is not busy anymore.
-h Print help message.
NOTE
For further information please refer nfs(5) and umount(8) manual pages.
FILES
/etc/fstab file system table
/etc/mtab table of mounted file systems
SEE ALSO
nfs(5), umount(8),
AUTHOR
Amit Gud <agud@redhat.com>
6 Jun 2006 UMOUNT.NFS(8)