EXT3-fs error Remounting filesystem read-only
 

Hello experts!
OS: SUSE 10 sp4 ppc64, kernel - 2.6.16.60-0.85.1-ppc64 SAN: DS5300

I configured multipath with link:
http://www.sourceware.org/lvm2/wiki/...active_passive

I have some trouble with errors with ext3 filesystem.
After few days i saw read only file system.


#dmesg
_journal_remove_journal_head: freeing b_frozen_data
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-12, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
JBD: barrier-based sync failed on dm-12 - disabling barriers
sd 1:0:1:1: SCSI error: return code = 0x00070000
end_request: I/O error, dev sdg, sector 24259912
device-mapper: multipath: Failing path 8:96.
printk: 204169 messages suppressed.
Buffer I/O error on device dm-12, logical block 3032443
lost page write due to I/O error on dm-12
Buffer I/O error on device dm-12, logical block 3047989
lost page write due to I/O error on dm-12
Buffer I/O error on device dm-12, logical block 3032444
Buffer I/O error on device dm-12, logical block 3047990
lost page write due to I/O error on dm-12
lost page write due to I/O error on dm-12
Buffer I/O error on device dm-12, logical block 3047991
Buffer I/O error on device dm-12, logical block 3032445
lost page write due to I/O error on dm-12
lost page write due to I/O error on dm-12
Aborting journal on device dm-12.
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
ext3_abort called.
EXT3-fs error (device dm-12): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
C02-OraDB-01:~ #

C02-OraDB-01:~ # multipath -ll
350000393880b3624 dm-4 IBM-ESXS,MBF2300RC
[size=279G][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 0:2:0:0 sda 8:0 [active][ready]
3600a0b80006e6b36000093fd50c6980b dm-0 IBM,1818 FAStT
[size=3.0T][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:2 sdk 8:160 [failed][faulty]
\_ round-robin 0 [prio=1][active]
\_ 1:0:1:2 sdh 8:112 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:2 sde 8:64 [failed][faulty]
3600a0b80006e6b36000093fb50c69795 dm-1 IBM,1818 FAStT
[size=600G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:0:1 sdj 8:144 [failed][faulty]
\_ round-robin 0 [prio=1][active]
\_ 1:0:1:1 sdg 8:96 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:1 sdd 8:48 [failed][faulty]
3600a0b80006e68940000960550c69aac dm-2 IBM,1818 FAStT
[size=800G][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 2:0:0:0 sdi 8:128 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:1:0 sdf 8:80 [failed][faulty]
\_ round-robin 0 [prio=1][enabled]
\_ 1:0:0:0 sdc 8:32 [active][ready]
350000393880b35ac dm-3 IBM-ESXS,MBF2300RC
[size=279G][features=0][hwhandler=0]
\_ round-robin 0 [prio=1][active]
\_ 0:6:0:0 sdb 8:16 [active][ready]
C02-OraDB-01:~ #

Unmount the filesystem, do an fsck on it and try again.

(none):~ # fsck.ext3 -a /dev/vg_oradata_1/lv_oradata_1
/dev/vg_oradata_1/lv_oradata_1: clean, 33/104857600 files, 6141985/209689600 blocks
(none):~ # fsck.ext3 -a /dev/vg_oradata_2/vg_oradata_2
/dev/vg_oradata_2/vg_oradata_2: clean, 260/78643200 files, 11055547/157260800 blocks


(none):~ # cat /etc/fstab
/dev/system/rootlv / ext3 acl,user_xattr 1 1
/dev/system/swaplv swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/vg_oradata_backup/lv_oradata_backup /oradata_backup ext3 acl,user_xattr 1 2
/dev/vg_oradata_1/lv_oradata_1 /oradata_1 ext3 acl,user_xattr 1 2
/dev/vg_oradata_2/vg_oradata_2 /oradata_2 ext3 acl,user_xattr 1 2

(none):~ # fsck.ext3 -a /dev/vg_oradata_backup/lv_oradata_backup
Buffer I/O error on device dm-13, logical block 0
Buffer I/O error on device dm-13, logical block 1
Buffer I/O error on device dm-13, logical block 2
Buffer I/O error on device dm-13, logical block 3
Buffer I/O error on device dm-13, logical block 0
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/vg_oradata_backup/lv_oradata_backup
Could this be a zero-length partition?
(none):~ #

What do you mean and did it ever work?

What do you mean