bdf command hanging

[-_]

Dear supports,

Here iam our hp-ux system unable to read file system so when i use bdf command no output & not responding.

When iam trying to view from sam-disks&filesystem-filesystem status is reading but no output under / filesystem.

here iam attaching out of some commands which is useful to trobleshoot.

let me know how to over come this issue.

Thanks & Regards,

satish reddy

[-_]

Its urgent to resolve this issue

[Naj]

Hello,

It would be issue with FS corrupted or FS full i guess but before that varify couples of things.

1. check mount point

#mount -l

2. could you please check any error in syslog.log

3. did you able to execute df command?

Thanks

BR

Naj

[-_]

Iam not able to execute commands df or bdf , I didn't find any error from syslog.log file.

i got output from mount -l

find the attachment for your requirements

[Naj]

Hello,

Based on syslog, your system has been  up too long and time time to upgrade firmware

Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ...
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks 
== 0xFE59CFE4,  flags == 0x0

I think that is one of causes this issue.

how about #mount -v ?

can you paste the output here

Thanks

BR

Naj

[V. Nyga]

Can you post:

ll /var/adm/syslog

date

V.

[-_]

Dear Naj,

out put for mount -v

# mount -v
/dev/vg00/lvol3 on / type vxfs log on Wed Aug 26 09:14:24 2009
/dev/vg00/lvol1 on /stand type hfs defaults on Wed Aug 26 09:14:26 2009
/dev/vg00/lvol8 on /var type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:34 2009
/dev/vg00/lvol7 on /usr type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:34 2009
/dev/vg00/lvol6 on /tmp type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:34 2009
/dev/vg00/lvol9 on /oracle type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:34 2009
/dev/vg03/lvol1 on /orabkp type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:34 2009
/dev/vg00/lvol5 on /opt type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:35 2009
/dev/vg01/lvol1 on /iwdmsdb_dr type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:35 2009
/dev/vg00/lvol10 on /infra_db type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:35 2009
/dev/vg00/lvol4 on /home type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:35 2009
/dev/vg02/lvol1 on /archive_log type vxfs delaylog,nodatainlog on Wed Aug 26 09:14:35 2009
#

[-_]

# ll /var/adm/syslog
total 4203232
-rw-r--r--   1 root       root         22927 Aug 26  2009 OLDsyslog.log
-r--r--r--   1 root       root       4523584 Jul  4 13:14 mail.log
-rw-r--r--   1 root       root       2147483647 Jan  8 16:32 syslog.log

# date
Mon Jul  4 20:15:52 IST 2011
#

[V. Nyga]

:-)

your logfile is much to big
Use for example SAM to 'trim' your logfiles!

Then check for the current messages in syslog.

[-_]

I didn't find any recent logs

# tail -20 /var/adm/syslog/syslog.log
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFDB,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFDA,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD9,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD8,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD7,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD6,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD5,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD4,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD3,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD2,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD1,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFD0,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCF,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCE,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCD,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCC,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCB,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFCA,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFC9,  flags == 0x0
Jan  8 16:32:54 riwdmsdb vmunix: function == 0x92C520, arg == 0x42A31800, ticks
== 0xFE59CFC8,  flags == 0x0
Jan  8 16:32:54 riwdmsdb#