yeap. Thank you for your patience.

1-
# umount /bmc
# cd /bmc
# ls

2-
# service netfs restart
Mounting NFS filesystems: mount: imcltdd1-10g.mycompany.com:

Setting up Logical Volume Management: 1 logical volume(s) in volume group "oraworkvg1" now active
10 logical volume(s) in volume group "orahomevg1" now active
8 logical volume(s) in volume group "vg_orabmctd10" now active
[ OK ]
Checking network-attached filesystems
[ OK ]
Mounting other filesystems: [ OK ]

3-
After restartng netfs, the /bmc is mounted andI can see the BMCBDA directory

# cd /bmc
# ls
BMCBDA

I wonder why this doesn't kick in at reboot time.

THX, eg

is it set to run on boot? what does "chkconfig --list" say about it? if it's not on, run "chkconfig --levels 35 netfs on"

It was off. I turned it on.
I will reboot the server to test. THX, eg

Hello,

maybe i'm wrong,

http://linux.about.com/library/cmd/b...uto.master.htm

I thought he couldn't see files at reboot because of the autofs doesn't check auto.master and so the file system mounted at the boot.

Would you please correct my mistake? I could be easily wrong maybe.

It worked. After the reboot the NAS share was mounted on /bmc.

Thank you Chis and everybody else.
Truly appreciated.

auto.master is for autofs, which doesn't use fstab at all. Essentially it's wholly separate system that does a different job. Mounting network drives through autofs is useful as it will unmount when the drive is not in use, but in a server environment where there is always usage of them, and a reliable wired network, there is much more logic in using a static mount in fstab.

1 members found this post helpful.

Thank you Acid I learnt something more.