What kind of HDS array and why is it added a JBOD ?

c6              JBOD            ENABLED    jbod0
c7              JBOD            ENABLED    jbod0 


--- "Tony T." <[EMAIL PROTECTED]> wrote:

> Hi all,
> 
> We had a situation recently on an old 450 with dual 
> LP9002L   cards.  It's
> connected to a Hitachi SAN -- when I do a vxdisk
> list on each SAN disk I see
> two paths.  I do not see two paths listed for the
> internal drives.   Anyway,
> there was some maintenance on the SAN switches and
> the SAN guys assumed they
> could fail over their swtiches and our box would
> fail over on its own, but
> it did not.  In fact, the /var/adm/messages is full
> of vx errors all
> complaining about this event:
> 
> ( hostname changed for obvious reasons)
> 
> Sep  3 06:07:05 hostname vxdmp: [ID 619769
> kern.notice] NOTICE: vxdmp: Path
> failure on 32/0xa54
> Sep  3 06:07:05 hostname vxdmp: [ID 997040
> kern.notice] NOTICE: vxvm:vxdmp:
> disabled path 32/0xa50 belonging to the dmpnode
> 252/0x60
> Sep  3 06:07:06 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd345):
> Sep  3 06:07:06 hostname         SCSI transport
> failed: reason 'tran_err':
> giving up
> Sep  3 06:09:42 hostname scsi: [ID 365881 kern.info]
> <HITACHI-DF600F-0000 cyl 3930 alt 2 hd 50 sec 768>
> Sep  3 06:09:42 hostname vxdmp: [ID 912507
> kern.notice] NOTICE: vxvm:vxdmp:
> enabled path 32/0xa50 belonging to the dmpnode
> 252/0x60
> Sep  3 06:11:41 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd386):
> Sep  3 06:11:41 hostname         SCSI transport
> failed: reason 'tran_err':
> retrying command
> Sep  3 06:11:41 hostname lpfc: [ID 346038 kern.info]
> NOTICE:
> lpfc1:039:Cannot issue FCP command  Data: 0 1 0 0
> Sep  3 06:11:41 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd420):
> Sep  3 06:11:41 hostname         SCSI transport
> failed: reason 'tran_err':
> retrying command
> Sep  3 06:11:41 hostname lpfc: [ID 346038 kern.info]
> NOTICE:
> lpfc1:039:Cannot issue FCP command  Data: 0 1 0 0
> Sep  3 06:11:43 hostname last message repeated 2
> times
> Sep  3 06:11:43 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],4 (sd423):
> Sep  3 06:11:43 hostname         SCSI transport
> failed: reason 'tran_err':
> retrying command
> Sep  3 06:11:43 hostname lpfc: [ID 346038 kern.info]
> NOTICE:
> lpfc1:039:Cannot issue FCP command  Data: 0 1 0 0
> Sep  3 06:11:51 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd386):
> Sep  3 06:11:51 hostname         SCSI transport
> failed: reason 'tran_err':
> giving up
> Sep  3 06:11:51 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 (sd386):
> Sep  3 06:11:51 hostname         SCSI transport
> failed: reason 'tran_err':
> giving up
> Sep  3 06:11:51 hostname scsi: [ID 107833
> kern.warning] WARNING:
> /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],1 (sd420):
> Sep  3 06:11:51 hostname         SCSI transport
> failed: reason 'tran_err':
> giving up
> 
> 
> # vxdmpadm listctlr all
> CTLR-NAME       ENCLR-TYPE      STATE     
> ENCLR-NAME
>
=====================================================
> c0              OTHER           ENABLED    others0
> c3              OTHER           ENABLED    others0
> c4              OTHER           ENABLED    others0
> c5              OTHER           ENABLED    others0
> c2              OTHER           ENABLED    others0
> c6              JBOD            ENABLED    jbod0
> c7              JBOD            ENABLED    jbod0
> 
> c6 and c7 are the two HBAs.
> 
> sandg01 is one of the SAN disks:
> 
> # vxdisk list sandg01
> Device:    c6t0d0s2
> devicetag: c6t0d0
> type:      sliced
> hostid:    s006a01
> disk:      name=sandg01 id=1114981176.3728.s006a01
> group:     name=sandg id=1114981178.3731.s006a01
> flags:     online ready private autoconfig
> autoimport imported
> pubpaths:  block=/dev/vx/dmp/c6t0d0s4
> char=/dev/vx/rdmp/c6t0d0s4
> privpaths: block=/dev/vx/dmp/c6t0d0s3
> char=/dev/vx/rdmp/c6t0d0s3
> version:   2.1
> iosize:    min=512 (bytes) max=256 (blocks)
> public:    slice=4 offset=0 len=150873600
> private:   slice=3 offset=1 len=38399
> update:    time=1157307810 seqno=0.42
> headers:   0 248
> configs:   count=1 len=28326
> logs:      count=1 len=4291
> Defined regions:
>  config   priv 000017-000247[000231]: copy=01
> offset=000000 enabled
>  config   priv 000249-028343[028095]: copy=01
> offset=000231 enabled
>  log      priv 028344-032634[004291]: copy=01
> offset=000000 enabled
> Multipathing information:
> numpaths:   2
> c6t0d0s2        state=enabled
> c7t1d0s2        state=enabled
> 
> 
> The errors went on until all SAN disk was completely
> unavailable and I have
> 30 megs of "Uncorrectable read errors" on all SAN
> mount points in the
> messages file; the only way to fix this was to bring
> the box down, fsck all
> of the mangled SAN mount points and bring it back
> up.
> 
> What else should I be looking at here?
> > _______________________________________________
> Veritas-vx maillist  - 
> Veritas-vx@mailman.eng.auburn.edu
>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
> 



                
____________________________________________________ 
Do you Yahoo!? 
Listen to your personal radio station on Yahoo!7 Music 
http://au.music.yahoo.com/launchcast/setup.asp
_______________________________________________
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx

Reply via email to