[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9773.0. "advfs i/o error bs_osf_complete" by MIPSBX::"003/[email protected]" ([email protected]) Mon May 12 1997 03:30

Hi,

   I have 8200 in decsafe environment with SW300&Hsz40 Array controllers
system displayed a error " bs_osf_complete: metadata write failed Advfs
Domain Panic advfs I/O error on xyz domain"
when i rebooted the system still xyz domain disk was not able to mount I then
did a shutdown of sw300 & started again, then i booted the system & then
disk with xyz domain was mounted.

   When this error appeared the system was shutdown but the other system
which is in the decsafe environment was also not able to mount this xyz
domain when i saw the log file i was showing " reservation reset on the 
system which had mounted earlier"

   I have applied all the related patches from patch kit june 96.
my current ver are as follows.

1. osf/1    3.2c
2. ase      1.2
3. hsof     2.7

  Pl give me the in puts...

Thanks in Advance

Sachin (MCS MUMBAI, India)

 


[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
9773.1KITCHE::schottEric R. Schott USG Product ManagementMon May 12 1997 04:3333
>
>   I have 8200 in decsafe environment with SW300&Hsz40 Array controllers
>system displayed a error " bs_osf_complete: metadata write failed Advfs
>Domain Panic advfs I/O error on xyz domain"
>when i rebooted the system still xyz domain disk was not able to mount I then
>did a shutdown of sw300 & started again, then i booted the system & then
>disk with xyz domain was mounted.

Sounds like some type of problem with the sw300...have you looked
into later firmware revs (like V3.1?)

Were ther error log entries prior to this to give clues to the
error...

V3.2 C is kind of old...I expect all the error data was not
gathered..you should be running V3.2G with patch kits...this
will get better error log info from the hsz (with the
new hsz firmware....)


>
>   When this error appeared the system was shutdown but the other system
>which is in the decsafe environment was also not able to mount this xyz
>domain when i saw the log file i was showing " reservation reset on the 
>system which had mounted earlier"
>
>   I have applied all the related patches from patch kit june 96.
>my current ver are as follows.
>
>1. osf/1    3.2c
>2. ase      1.2
>3. hsof     2.7
>
9773.2NNTPD::"003/[email protected]"[email protected]Mon May 12 1997 05:3625
Hi,

Thanks for your reply


   similar kind of error had come earlier but that time we just rebooted
the system & it worked, we did not reboot Sw300.
Lastime when the error had come it was more than month ago. Both these
times there was no activity on the system, it happened early in the 
morning.

   will the hsof ver upgrade help ? 

The systems are installed more than year back but these errors
are seen only twice in lat one month.

   do you thing osf/1 upgrade to 3.2g will help ?


Thanks once again

Sachin


[Posted by WWW Notes gateway]
9773.3KITCHE::schottEric R. Schott USG Product ManagementTue May 13 1997 04:0935
>
>
>   similar kind of error had come earlier but that time we just rebooted
>the system & it worked, we did not reboot Sw300.
>Lastime when the error had come it was more than month ago. Both these
>times there was no activity on the system, it happened early in the 
>morning.
>
>   will the hsof ver upgrade help ? 

Hi

 I think and upgrade with patches may help...as well as ensure all
firmware revs are upto date.

You should verify that the advfs domain is ok...you should check
in the advfs notes conference on how to do this on V3.2*...on V4.0* you
would use verify(8)

The upgrade to V3.2G with patches and firmware should allow you
to get better error log data...and ensuring the advfs domain is
ok prior to using would ensure we are not chasing any pre-existing
problem.

>
>The systems are installed more than year back but these errors
>are seen only twice in lat one month.
>
>   do you thing osf/1 upgrade to 3.2g will help ?
>

Note I'm not sure if you have an hsz or OS problem...I'm suggesting the
above so you can get better error log data an avoid knwon or
pre-existing problems.