Ignite backup problem ?

[rveri]

Hi All ,

Found Ignite backup failed, from the logfile.
While re-running getting this error message continously :

"NFS server srv-abc not responding still trying."

details:

* bdf hangs

* bdf -l : works fine ,all local filesystems shows.

* tried to ping the server srv-abc , its pingable.

* found someone earlier mounted one nfs filesystem , from srv-abc server : ( using this command : # mount -F nfs srv-abc:/mnt/fs1 /remotefs ) , and now this filesystem is no longer available , causing bdf to hang. Even # cd /remotefs hangs.



Whats wrong. What can be done , to unmount that filesystem.

I have tried :

# umount /remotefs
nfs umount: nfs_unmount: /remotefs: is busy
umount: return error 1.


Pls suggest.

Thanks ,

[njia_1]

Hi

Just like what you said, the remote file system is not longer available and that is why bdf hangs.

Have you tried to stop/restart nfs.server and nfs.client ?

Are you doing an ignite backup cross the network ?

Have a look at ignite's man page, there may be an option to by pass that directory.

thanks

[Devender Khatana]

Hi,

use fuser to kill the processes using files in this file system if any.

#fuser -ck /remotefs

The try unmounting it. If do not succed then if there are no other NFS file systems exported/imported from this server do

#/sbin/init.d/nfs.client stop

#/sbin/init.d/nfs.server stop

#/sbin/init.d/nfs.core stop

If the issue gets resolved by this then restart the services again.

HTH,
Devender

[Devender Khatana]

Hi Again,

The earlier post actually concerned about the bdf problem only. So for the ignite problem I think you should specify to backup only vg00 using -x switch.

Still it may give problem as it will use bdf and fstab to find out the currently unmounted file systems without which it can not proceed.

HTH,
Devender

[rveri]

Devender ,

This is the command I am using for Ignite backup :

* /opt/ignite/bin/make_tape_recovery -A -v -a /dev/rmt/0mn -x inc_entire=vg00 -n 2

* Also this is a adoptive node of a 2 node cluster . Will be there any impact , if the nfs.client stop , nfs.server stop & nfs.core stop , executes.

Please suggest.

Thanks.

[Devender Khatana]

Hi,

If it is part of cluster, then I would recommend to reboot it as the other node will take care of applications. The impact may there if some of the packages require NFS services.

HTH,
Devender

[njia_1]

Hi there,

do a nfs.server stop/start and nfs.client stop/start on the adoptive node should not have any impact on the packages as long as the package is not running on the adoptive node.

do a showmount -e first on that node to see if any file system being exported.

thanks

[rveri]

Hi ,

showmount shows the following error:


# showmount -e
showmount: infsrv12: RPC: Program not registered.

What could be the problem.

Thanks.

[Chauhan Amit]

Check out these Links with similar problem,

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=986938

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=106047

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=938994

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=68070

-Amit

[Muthukumar_5]

It is a problem with *NFS*.

Some body is trying to use /remotefs.

Check as,

# fuser -k /remotefs

It will release that file system usage.

# cd /
# umount /remotefs

It is unmounted now.

Try to restart NFS as,

# /sbin/init.d/nfs.server stop
# /sbin/init.d/nfs.server start

# /sbin/init.d/nfs.core stop
# /sbin/init.d/nfs.core start

# /sbin/init.d/nfs.client stop
# /sbin/init.d/nfs.client start

Check rpcinfo status for debugging.

--
Muthu