Conference ssdevo::hsz40_product

795.0. "error=6/0 on file command" by MANM01::NOELGESMUNDO () Wed Mar 05 1997 05:16

    Hello!
    
    I received this mail from a customer asking for an explanation. He
    believes his disk is going to 'crash' anytime so would like to know
    exactly what the message means. Please take note of the display after
    he issued the file command for a disk.
    
    Thanks.
    
    Noel Gesmundo
    MCS/Philippines
    
    ================================================================== 
    


                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     05-Mar-1997 02:52am HKT
                                        From:     Arnel M. Banzon
                                                  [email protected]@PMDF@INTERNET
                                        Dept:      
                                        Tel No:    

TO: See Below

Subject: disk  errors                                                           

Noelski,

Here are the details of the logs in decoded format. Please rename the
b2_logs.en to b2_logs.tar when you finish the decoding. In addition here
is the HSZ40 output for the domain:


# df -k
Filesystem         1024-blocks        Used       Avail Capacity  Mounted
on
root_domain#root         65536       45484       12888    78%    /
/proc                        0           0           0   100%    /proc
usr_domain#usr         1048576      605877      398792    60%    /usr
oracle#engine          2055240      908098      597456    60%    /oracle
oracle_data2#arch     20939944     3192542     4041528    44%   
/arch_logs
arch_logs#data         6162696     5587568      567600    91%    /bills
oracle_data#data      20939944    20268343      600800    97%   
/oracle_data
oracle_data2#data2    20939944    13679771     4041528    77%   
/oracle_data2
oracle_data3#data3    20939944    18744154     2185680    90%   
/oracle_data3
oracle#user            1000016      493526      506490    49%    /user
oracle#stat             100000        1187       98813     1%   
/stat_logs    

# showfdmn oracle_data2

               Id              Date Created  LogPgs  Domain Name
32f19f66.00001ab0  Fri Jan 31 15:29:42 1997     512  oracle_data2

  Vol   512-Blks        Free  % Used  Cmode  Rblks  Wblks  Vol Name
   1L   41879900     8117136     81%     on    128    128 
/dev/rzb130c        

# file /dev/rrzb130c
/dev/rrzb130c:  character special (8/264258) SCSI #16 HSZ40 disk #1041
(SCSI ID#2) errors = 6/0 

HSZ> show r3

Name          Storageset                     Uses             Used by
------------------------------------------------------------------------------

R3            raidset                        DISK120          D201
                                             DISK220
                                             DISK320
                                             DISK420
                                             DISK520
                                             DISK620
        Switches:
          POLICY (for replacement) = BEST_PERFORMANCE
          RECONSTRUCT (priority) = NORMAL
          CHUNKSIZE = 256 blocks
        State:
          NORMAL
          DISK120   (member  0) is NORMAL
          DISK220   (member  1) is NORMAL
          DISK320   (member  2) is NORMAL
          DISK420   (member  3) is NORMAL
          DISK520   (member  4) is NORMAL
          DISK620   (member  5) is NORMAL
        Size: 41879900 blocks
HSZ>                                                 

Need you soonest feedback to avoid downtime for bayan2.

Regards,

Arnel

Distribution:
 
TO:  Ley B. Salcedo                       ( [email protected]@PMDF@INTERNET )
TO:  gesmundo.noel                        ( gesmundo.noel@man )
TO:  mejia.jomar                          ( mejia.jomar@man )
TO:  matriano.jerome                      ( matriano.jerome@man )
 
CC:  ricoj                                ( [email protected]@PMDF@INTERNET )
CC:  caloy                                ( [email protected]@PMDF@INTERNET )

Use DECevent to look at the errorlog, and it should tell you
what the errors are all about.  The file command is just telling
you to look at the errorlog.

	Fred