服务器启动报SCSI错误，导致文件系统无法挂载，求高手指教！

七杀书生

内容可能有点多，我是希望大家能把情况弄清楚一些，才更利于分析和判断，希望大家可以看完，帮我分析一下。
我想了很多办法都解决不了，很急。。。

环境：
1、服务器：DELL 6850  两台
2、磁盘阵列：DELL PV220S 一台
3、操作系统：RedHat AS3

情况：
1、两台服务器通过SCSI线缆与PV220S相连，直接附加存储DAS。
2、磁盘阵列做RAID 5。在两台服务器看是一块硬盘sdb。
3、sdb两个分区，分别是：sdb1和sdb2。
4、sdb1挂载到服务器1上，sdb2挂载到服务器2上。

问题出现在23日凌晨给两台服务器做内存扩容，分别加了4G的内存，加上内存之后，把线连好，然后开机，启动服务器。
服务器1很正常，没有问题。
服务器2在启动时，有报错，如下：
scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 3960D Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
  
blk: queue f630e418, I/O limit 524287Mb (mask 0x7fffffffff)
scsi3:A:0:0: DV failed to configure device.  Please file a bug report against this driver.
(scsi3:A:0): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit)
  Vendor: TechSys   Model: 8312              Rev: 0001
  Type:   Direct-Access                      ANSI SCSI revision: 03
blk: queue f630e218, I/O limit 524287Mb (mask 0x7fffffffff)
scsi3:A:0:0: Tagged Queuing enabled.  Depth 32
Attached scsi disk sdb at scsi3, channel 0, id 0, lun 0
SCSI device sdb: 2867445760 512-byte hdwr sectors (1468132 MB)
sdb: sdb1 sdb2

服务器启动后，发现sdb2没有被挂载。
然后使用fdisk -l命令，可以看到sdb。
然后我执行手动挂载，失败。
然后我执行mount -t ext2 /dev/sdb2 /mnt/sdb2  有警告产生，但成功了。
EXT2-fs warning (device sd(8,1): ext2_read_super: mounting ext3 filesystem as ext2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

然后我执行tune2fs -j /dev/sdb2，失败了，报一下错误：
JBD: no valid journal superblock found
EXT3-fs: error loading journal.

然后我使用dmesg命令，得到大量自加内存以后的如下错误：
[root@crbt-web2 log]# dmesg
c18, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
  Vendor: PE/PV     Model: 1x5 SCSI BP       Rev: 1.0
  Type:   Processor                          ANSI SCSI revision: 02
blk: queue cb218a18, I/O limit 4294967295Mb (mask 0xffffffffffffffff)
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 143374650 512-byte hdwr sectors (73408 MB)
Partition check:
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
scsi2 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 3960D Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 3960D Ultra160 SCSI adapter>
        aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs

blk: queue f634c218, I/O limit 524287Mb (mask 0x7fffffffff)
scsi3:A:0:0: DV failed to configure device.  Please file a bug report against this driver.
(scsi3:A:0): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit)
  Vendor: TechSys   Model: 8312              Rev: 0001
  Type:   Direct-Access                      ANSI SCSI revision: 03
blk: queue f634c018, I/O limit 524287Mb (mask 0x7fffffffff)
scsi3:A:0:0: Tagged Queuing enabled.  Depth 32
Attached scsi disk sdb at scsi3, channel 0, id 0, lun 0
SCSI device sdb: 2867445760 512-byte hdwr sectors (1468132 MB)
sdbscsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
SCSI disk error : host 3 channel 0 id 0 lun 0 return code = 60000
I/O error: dev 08:10, sector 0
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x97) SCSIRATE(0xc2)
        CRC Value Mismatch
SCSI disk error : host 3 channel 0 id 0 lun 0 return code = 60000
I/O error: dev 08:10, sector 0
unable to read partition table
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Freeing unused kernel memory: 228k freedusb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 00:25:07 Apr 22 2004
usb-uhci.c: High bandwidth mode enabled
PCI: Setting latency timer of device 00:1d.0 to 64
usb-uhci.c: USB UHCI at I/O 0x3ce0, IRQ 16
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.1 to 64
usb-uhci.c: USB UHCI at I/O 0x3cc0, IRQ 19
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Setting latency timer of device 00:1d.2 to 64
usb-uhci.c: USB UHCI at I/O 0x3ca0, IRQ 18
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Setting latency timer of device 00:1d.7 to 64
ehci-hcd 00:1d.7: Intel Corp. 82801EB USB2
ehci-hcd 00:1d.7: irq 23, pci mem f88d6000
usb.c: new USB bus registered, assigned bus number 4
ehci-hcd 00:1d.7: enabled 64bit PCI DMA
PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
PCI: 00:1d.7 PCI cache line size corrected to 128.
ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22
hub.c: USB hub found
hub.c: 6 ports detected
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,5), internal journal
Adding Swap: 4192924k swap-space (priority -1)
hub.c: connect-debounce failed, port 1 disabled
hub.c: new USB device 00:1d.7-3, assigned address 2
hub.c: USB hub found
hub.c: 2 ports detected
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,2), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,7), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,9), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hub.c: new USB device 00:1d.2-1, assigned address 2
input0: USB HID v1.10 Keyboard [Tripplite B015-000 R0.74 USB to PS2 adapter.] on usb3:2.0
input1: USB HID v1.10 Mouse [Tripplite B015-000 R0.74 USB to PS2 adapter.] on usb3:2.1
usb-uhci.c: ENXIO 84000280, flags 0, urb f60f1600, burb f60f1c00
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 84000280, flags 0, urb f60f1580, burb f60f1c00
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 84000280, flags 0, urb f6e7bc80, burb f60f1c00
usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
microcode: No suitable data for cpu 2
microcode: No suitable data for cpu 1
microcode: No suitable data for cpu 3
microcode: No suitable data for cpu 0
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa3) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa3) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa3) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa3) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa3) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0xa4) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
(scsi3:A:0:0): parity error detected in Data-in phase. SEQADDR(0x9f) SCSIRATE(0xc2)
        CRC Value Mismatch
Attached scsi generic sg1 at scsi0, channel 0, id 6, lun 0,  type 3inserting floppy driver for 2.4.21-15.ELsmp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
tg3.c:v3.1 (April 3, 2004)
divert: allocating divert_blk for eth0
eth0: Tigon3 [partno(BCM95704CA40-I) rev 2003 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:10:18:06:a9:2a
eth0: HostTXDS[0] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth1
eth1: Tigon3 [partno(BCM95704CA40-I) rev 2003 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:10:18:06:a9:2b
eth1: HostTXDS[0] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth2
eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0f:1f:ff:bd:96
eth2: HostTXDS[0] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth3
eth3: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0f:1f:ff:bd:97
eth3: HostTXDS[0] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
divert: freeing divert_blk for eth0
divert: freeing divert_blk for eth1
divert: freeing divert_blk for eth2
divert: freeing divert_blk for eth3
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (8192 buckets, 65536 max) - 304 bytes per conntrack
tg3.c:v3.1 (April 3, 2004)
divert: allocating divert_blk for eth0
eth0: Tigon3 [partno(BCM95704CA40-I) rev 2003 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:10:18:06:a9:2a
eth0: HostTXDS[0] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth1
eth1: Tigon3 [partno(BCM95704CA40-I) rev 2003 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:10:18:06:a9:2b
eth1: HostTXDS[0] RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth2
eth2: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0f:1f:ff:bd:96
eth2: HostTXDS[0] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
divert: allocating divert_blk for eth3
eth3: Tigon3 [partno(BCM95704A6) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:0f:1f:ff:bd:97
eth3: HostTXDS[0] RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
tg3: eth1: Link is up at 100 Mbps, full duplex.
tg3: eth1: Flow control is off for TX and off for RX.
tg3: eth3: Link is up at 100 Mbps, full duplex.
tg3: eth3: Flow control is off for TX and off for RX.
audit subsystem ver 0.1 initialized
Audit daemon registered (process 6456)
lp: driver loaded but no devices found
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).



然后我查看cat /var/log/messages
我把这个message用附件传上来，希望大家可以帮我看看，分析分析。。
messages.rar (34.24 KB, 下载次数: 11)

2010-03-24 19:19 上传

点击文件名下载附件

谢谢各位

七杀书生

自己顶一下，希望有高手指教，很急！！！谢谢

jerryjzm

你在哪台ok的服务器上
df -Th
看看内容，
---------------------------------------------------------------------------------------------------------------
然后我执行mount -t ext2 /dev/sdb2 /mnt/sdb2  有警告产生，但成功了。
EXT2-fs warning (device sd(8,1): ext2_read_super: mounting ext3 filesystem as ext2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
---------------------------------------------------------------------------------------------------------------
这里说明了，你将ext3的文件系统挂成了ext2了，我想看看你哪台机器到底是什么格式的文件系统

lcmust

然后我执行手动挂载，失败。
然后我执行mount -t ext2 /dev/sdb2 /mnt/sdb2  有警告产生，但成功了。
EXT2-fs warning (device sd(8,1): ext2_read_super: mounting ext3 filesystem as ext2
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended

然后我执行tune2fs -j /dev/sdb2，失败了，报一下错误：
JBD: no valid journal superblock found
EXT3-fs: error loading journal.
-------------------------------------------------------------------------------------------
这是什么意思： 手动挂载失败！   下面用命令挂载又“成功”

确实是将 ext3 挂载成了ext2. 所以有警告。。。。。。
（重新用 -t ext3 挂载，看看呢）

aramis

100%确认的告诉你，这样用是有问题的，而且情况很糟糕{:3_188:}

220s有三种工作模式，join-bus和split及cluster，
照你的描述肯定是用的join-bus模式，那么两台机器的raid卡，硬盘及背板首先在一个物理总线上边，如果没有改过卡的ID，那么默认都是7，这样是不允许的

从logical bus来讲，同时只有一个控制器可以占用这个总线，根本不允许两个卡同时去操作一个总线的同一个设备，除非通过集群软件来进行控制。

之前你怎么用的，而且还是好的我没有能力去解释，但是你这个用法肯定是错的，

solution：备份你的数据，并只开一台机器检查文件系统。
后续操作就是将220设置为split模式，更换硬盘槽位，做两个raid，分配给两个机器来用

七杀书生

回复 5# aramis


    谢谢您的指点，我正在努力尝试解决。有问题再请教您