是否阵列出现问题

东方蜘蛛

硬盘灯有米亮呀，是不是掉电了

东方蜘蛛

看看控制器的状态灯，telnet到T3里面看看fru stat、vol stat的状态

东方蜘蛛

看看T3的syslog，如果所有磁盘和volume都正常的话，就可能是链路上引起的！\r\n可以先从OS层检查,看看HBA卡的状态灯：\r\n# format\r\n# luxadm -e port\r\n# fcinfo hba-port

lhz750320

T3的syslog\r\nJan 15 14:51:06 ROOT[0]: N: Initializing software...\r\nJan 15 14:51:19 ROOT[1]: N: u1ctr Initializing loop 1 ISP2100 ... firmware status = 3\r\nJan 15 14:51:19 ROOT[1]: N: u1ctr Detected 10 FC-AL ports on loop 1\r\nJan 15 14:51:37 ROOT[1]: N: u1ctr Initializing loop 2 ISP2100 ... firmware status = 3\r\nJan 15 14:51:37 ROOT[1]: N: u1ctr Detected 10 FC-AL ports on loop 2\r\nJan 15 14:51:53 ROOT[1]: N: 10 fcal ports were detected on l1\r\nJan 15 14:51:53 ROOT[1]: N: 10 fcal ports were detected on l2\r\nJan 15 14:51:59 ROOT[1]: N: u1ctr opening disk driver swap manager\r\nJan 15 14:51:59 ROOT[1]: N: u1ctr reading disk info\r\nJan 15 14:51:59 ROOT[1]: N: u1ctr found 9 disks in system\r\nJan 15 14:51:59 ROOT[1]: N: u1 initializing system area\r\nJan 15 14:51:59 ROOT[1]: N: u1 verifying system area\r\nJan 15 14:52:04 ROOT[1]: N: u1ctr Mounting root volume...\r\nJan 15 14:52:04 ROOT[1]: N: u1ctr Checking local file system...\r\nJan 15 14:52:12 ROOT[1]: N: u1ctr Initializing network routes...\r\nJan 15 14:52:12 ROOT[1]: N: u1ctr Read PGR data ... \r\nJan 15 14:52:12 ROOT[1]: N: u1ctr Done. \r\nJan 15 14:52:12 ROOT[1]: N: u1ctr Starting Syslog Daemon...\r\nJan 15 14:52:12 ROOT[1]: N: T300 Release 1.17b 2001/05/31 17:47:22 (172.28.1.211)\r\nJan 15 14:52:12 ROOT[1]: W: u1ctr SysFail Reset (7001) was initiated at 20090115 145013 Cache memory parity error detected\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr System has 1 active controller(s)\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Initializing TFTP...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting ftpd...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting telnetd...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting timed...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting pshd...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting httpd...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting snmpd...\r\nJan 15 14:52:14 snmp[1]: N: snmpd cold start\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Starting schd...\r\nJan 15 14:52:14 ROOT[1]: N: u1ctr Checking disk positions...\r\nJan 15 14:52:18 ROOT[1]: N: u1ctr Initializing host port u1p1 ISP2100 ... firmware status = 7\r\nJan 15 14:52:18 ROOT[1]: N: u1ctr Host port u1p1 TARGET_ID = 0xffff (ALPA = 0x7c)\r\nJan 15 14:52:20 ROOT[1]: N: u1ctr Starting psh...\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] Received LIP(f0,f0) async event\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] qlcf_sync_pdb: PDB Sync Initiated (host id 125)\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] qlcf_update_pdb: PDB Sync Done (host id 125)\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] PDB Sync Done (host id 125, host WWN 2001080020acf0a0)\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] qlcf_sync_pdb: PDB Sync Initiated (host id 124)\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] qlcf_update_pdb: PDB Sync Done (host id 124)\r\nJan 15 14:52:20 ISR1[1]: N: u1ctr ISP2100[2] PDB Sync Done (host id 124, host WWN 2001080020acf4ef)\r\nJan 15 14:52:20 FCC0[1]: N: u1ctr PDB Changed on port 0 (id 125)\r\nJan 15 14:52:20 FCC0[1]: N: u1ctr PDB Changed on port 0 (id 124)\r\nJan 15 14:52:20 FCC0[1]: N: u1ctr (ITL 7C 1 1 TT 20 TID 9690 OP 2A) Target in Unit Attention\r\nJan 15 14:52:21 FCC0[1]: N: u1ctr (ITL 7D 1 0 TT 20 TID 969C OP 2A) Target in Unit Attention\r\n\r\nroot@dbserver # luxadm -e port\r\n\r\nFound path to 4 HBA ports\r\n\r\n/devices/sbus@3,0/SUNW,socal@d,10000:0                             CONNECTED\r\n/devices/sbus@3,0/SUNW,socal@d,10000:1                             CONNECTED\r\n/devices/sbus@a,0/SUNW,socal@d,10000:0                             NOT CONNECTED\r\n/devices/sbus@a,0/SUNW,socal@d,10000:1                             NOT CONNECTED\r\n\r\nroot@dbserver # fcinfo hba-port\r\nfcinfo: not found

lhz750320

求助高手，快来帮忙呀

xiazhen9842

我感觉肯定不是硬盘的问题，线的可能性最大。你还是先换一下线、或者光纤接口之类的。。从上面信息来看，好像连接有点不大正常。肯定不是硬盘的问题。

lhz750320

在网上查找大致解决方法，要求先删除磁盘组，重现装载，不知道这方法能适合我公司这种情况么

lhz750320

T3外接的线缆应该没问题，不知道是否是T3内部的链接有问题

fenglimian

系统时间和盘阵的时间不一致吧,感觉你碰到的问题是T3的一个控制器重启了:\r\nJan 15 15:14:59 apserver socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.5010] socal0: port 1: Fibre Channel is OFFLINE\r\nJan 15 15:14:59 apserver socal: [ID 403145 kern.info] ID[SUNWssa.socal.link.6010] socal0: port 1: Fibre Channel Loop is ONLINE\r\n\r\n然后OS层连接到这个控制器的LUN失效:\r\nJan 15 15:14:59 apserver scsi: [ID 243001 kern.info] /sbus@2,0/SUNW,socal@d,10000/sf@1,0 (sf1):\r\nJan 15 15:14:59 apserver         ELS 0x3 recvd from target 0x7d\r\nJan 15 15:14:59 apserver scsi: [ID 243001 kern.info] /sbus@2,0/SUNW,socal@d,10000/sf@1,0 (sf1):\r\nJan 15 15:14:59 apserver         target 0x1 al_pa 0xe8 lun 1 offlined\r\n\r\n再然后DMP就查看到了这个LUN的失效:\r\nJan 15 15:14:59 apserver vxdmp: [ID 997040 kern.notice] NOTICE: vxvm:vxdmp: disabled path 118/0x20 belonging to the dmpnode 263/0x40\r\nJan 15 15:14:59 apserver vxdmp: [ID 148046 kern.notice] NOTICE: vxvm:vxdmp: disabled dmpnode 263/0x40\r\n\r\n后面的日志中还有:\r\nJan 15 15:22:03 apserver vxdmp: [ID 912507 kern.notice] NOTICE: vxvm:vxdmp: enabled path 118/0x20 belonging to the dmpnode 263/0x40\r\nJan 15 15:22:03 apserver vxdmp: [ID 205910 kern.notice] NOTICE: vxvm:vxdmp: enabled dmpnode 263/0x40\r\n说明这个时候物理链路连通后,OS认到的设备没有了问题,DMP也重新标记这个设备是可用的.\r\n\r\n你可以用vxdisk list db-dg02这个盘,然后用format命令去看它们active的path,如果format没有问题,就说明实际上物理链路和array此时可用,最简单的办法就是umount文件系统,deport DG,然后vxdisk list就应该是看到所有设备都是online的,然后import DG,让卷自己同步就好.\r\n\r\n\r\n我刚查了一下手册,如果format看到的设备都没有问题,还可以做vxreattach -c db-dg02去检查一下收费可以做reattach,然后没有提示什么问题,就用vxreattach -rb db-dg02来做reattach,相应做vxrecover之类就好了.\n\n[ 本帖最后由 fenglimian 于 2009-1-19 14:01 编辑 ]