bdf hangs

hi,

bdf command hangs but before it, it lists all the fstab content, so i cannot find the reason...

could anybody give me any clue??

thanks a lot for your attention.

regards

Pablo

i attach syslog

Jan 14 16:30:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:30:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:31:34 sv23  above message repeats 9 times
Jan 14 16:35:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:35:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:37:03 sv23  above message repeats 9 times
Jan 14 16:40:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:40:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:43:50 sv23  above message repeats 9 times
Jan 14 16:45:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:45:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d
Jan 14 16:46:57 sv23  above message repeats 9 times
Jan 14 16:50:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d

Please post the output from:

type bdf
cat /etc/fstab
cat /etc/mnttab
mount

Any context or buildup? Have you have been manually editing /etc/fstab or making other changes? Any recent hardware failures?

cat /etc/fstab
# System /etc/fstab file.  Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg00/lvcrash /var/adm/crash vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg00/lvapps /apps vxfs delaylog 0 2
/dev/vg00/lvproducts /products vxfs delaylog 0 2
/dev/vg00/lvlogs /logs vxfs delaylog 0 2
/dev/vg00/lvtools /tools vxfs delaylog 0 2
/dev/vg00/lvtransfer /transfer vxfs delaylog 0 2
/dev/vg00/lvoracle /oracle vxfs delaylog,nodatainlog 0 2
/dev/vg00/lvbte /bte vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg00/lvlocal /local vxfs delaylog 0 2
/dev/vg00/lvoraarc /oraarc vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2
/dev/vg01/lvoradbf1 /oradbf1 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg01/lvoradbf2 /oradbf2 vxfs rw,suid,largefiles,delaylog,datainlog 0 2


/dev/vg00/lvol3 / vxfs log 0 1 1322822033
/dev/vg00/lvol1 /stand hfs defaults 0 0 1322822034
/dev/vg00/lvol8 /var vxfs delaylog,nodatainlog 0 0 1322822042
/dev/vg00/lvcrash /var/adm/crash vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822042
/dev/vg00/lvol7 /usr vxfs delaylog,nodatainlog 0 0 1322822042
/dev/vg00/lvtransfer /transfer vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvtools /tools vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvol4 /tmp vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvproducts /products vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg01/lvoradbf2 /oradbf2 vxfs delaylog,nodatainlog,largefiles 0 0 1322822043
/dev/vg01/lvoradbf1 /oradbf1 vxfs delaylog,nodatainlog,largefiles 0 0 1322822043
/dev/vg00/lvoracle /oracle vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvoraarc /oraarc vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822043
/dev/vg00/lvol6 /opt vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvlogs /logs vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvlocal /local vxfs delaylog,nodatainlog 0 0 1322822044
/dev/vg00/lvol5 /home vxfs delaylog,nodatainlog 0 0 1322822044
/dev/vg00/lvbte /bte vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822044
/dev/vg00/lvapps /apps vxfs delaylog,nodatainlog 0 0 1322822044
sv55adm:/var/opt/ignite/clients /var/opt/ignite/recovery/client_mnt nfs rsize=65536,wsize=65536,NFSv3 0 0 1324000801
sv55adm:/var/opt/ignite/recovery/archives/sv23 /var/opt/ignite/recovery/arch_mnt nfs rsize=65536,wsize=65536,NFSv3 0 0 1324000976
sv23:#/root# ca
sv23:#/root# clear
sv23:#/root# cat /etc/mnttab
/dev/vg00/lvol3 / vxfs log 0 1 1322822033
/dev/vg00/lvol1 /stand hfs defaults 0 0 1322822034
/dev/vg00/lvol8 /var vxfs delaylog,nodatainlog 0 0 1322822042
/dev/vg00/lvcrash /var/adm/crash vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822042
/dev/vg00/lvol7 /usr vxfs delaylog,nodatainlog 0 0 1322822042
/dev/vg00/lvtransfer /transfer vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvtools /tools vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvol4 /tmp vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvproducts /products vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg01/lvoradbf2 /oradbf2 vxfs delaylog,nodatainlog,largefiles 0 0 1322822043
/dev/vg01/lvoradbf1 /oradbf1 vxfs delaylog,nodatainlog,largefiles 0 0 1322822043
/dev/vg00/lvoracle /oracle vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvoraarc /oraarc vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822043
/dev/vg00/lvol6 /opt vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvlogs /logs vxfs delaylog,nodatainlog 0 0 1322822043
/dev/vg00/lvlocal /local vxfs delaylog,nodatainlog 0 0 1322822044
/dev/vg00/lvol5 /home vxfs delaylog,nodatainlog 0 0 1322822044
/dev/vg00/lvbte /bte vxfs delaylog,nodatainlog,nolargefiles 0 0 1322822044
/dev/vg00/lvapps /apps vxfs delaylog,nodatainlog 0 0 1322822044
sv55adm:/var/opt/ignite/clients /var/opt/ignite/recovery/client_mnt nfs rsize=65536,wsize=65536,NFSv3 0 0 1324000801
sv55adm:/var/opt/ignite/recovery/archives/sv23 /var/opt/ignite/recovery/arch_mnt nfs rsize=65536,wsize=65536,NFSv3 0 0 1324000976

ok i see, the last entry of this file is the one who is hang

but when i try to unmmount

says it busy

sv55adm:/var/opt/ignite/recovery/archives/sv23 /var/opt/ignite/recovery/arch_mnt nfs rsize=65536,wsize=65536,NFSv3 0 0 1324000976
sv23:#/root# umount /var/opt/ignite/recovery/arch_mnt
nfs umount: nfs_unmount: /var/opt/ignite/recovery/arch_mnt: is busy
umount: return error 1.
sv23:#/root# umount sv55adm:/var/opt/ignite/recovery/archives/sv23
nfs umount: nfs_unmount: /var/opt/ignite/recovery/arch_mnt: is busy
umount: return error 1.

and when i do

user -k /var/opt/ignite/recovery/arch_mnt
/var/opt/ignite/recovery/arch_mnt:

is like stalled... so i have to do control-c

Sorry, but I have absolutely no idea what is going on here. Please review your post and ensure that the commands match the output and that there are four different commands with matching output. If your /etc/fstab is as posted, it is so corrupt that it will not work. I suspect a mispost.

Are you running from an Ignite recovery or some sort?

well,

ignite is configured in this server(client) to make it to the ignite server sv55

so, seems that it lost connection or anything, and now i cannot umount that sv55adm entry in mnttab, even if i kill processes related with ignite, and make fuser -ck to the mount point.

ignite is just configured in the crontab and the mount point is created automatically

you found the issue. it's your NFS mounts that are hung. make sure your sv55adm server is alive and on the network, then perform various network connection tests. you may have to reboot your sv23 server to clear the stale NFS mounts, if can't force them to umount.

Please be specific (including showing the relevant crontab line). Is the computer with the problem using server "sv55adm" to store an ignite image?
Also, is this a new build or a sudden problem with an established system?

Please do edit post #3 so that commands match output. As posted it makes no sense.

First of all, it's bad practice to put NFS mounts in /etc/fstab
Use automount rather.

Why ? Cause network issues or nfs server issue can cause your entire machine to hang on boot.

For your problems actions you can take is :
0. Check NFS server. Problems related are probably due to misconfiguration on server for your client.

  1. Use lsof with grep to identify which process are being used on sv55adm, to kill them
  2. fuser -cku /mountpoint
  3. If everything else fails, stop nfs client and umount (other nfs mountpoints will also stop working.)

You can also use bdf -t vxfs to display just vxfs filesystems before issue is resolved.