Unsolved
This post is more than 5 years old
5 Posts
0
407
January 30th, 2009 01:00
Powerpath +SLES10SP1 not working on Dell 1950III ??
Hi,
we currently trying to replace some older SUN X4100 with Dell Poweredge 1950 III.
But we are running into some starnge problems. After 4-24h the filesystem switching to read only
and you have to fsck (or often reinstall!) the system!
Hardware: Dell 1950 III with Perc6i (Raid 1) with QLA2462
OS: SLES 10_SP1(64), EMCPower.LINUX.5.1.0.Patch.b194, Quantum SNFS 3.0.3.65
SAN is inactive (no zoning) only kernel modules are loaded.
Root fs is ext3
No load, nothing running on the machine. We have tested 2 different machines -> same error!
The only(!) message we get:
Aborting journal on device sda6.
ext3_abort called.
EXT3-fs error (device sda6): ext3_journal_start_sb: Detected aborted journal
Is anybody running SLES 10 SP1 on this hardware ?
Any idea what's going on ?
Yes, we have tried also news LSI driver (3.16 and 3.21)
Bye, Peer
we currently trying to replace some older SUN X4100 with Dell Poweredge 1950 III.
But we are running into some starnge problems. After 4-24h the filesystem switching to read only
and you have to fsck (or often reinstall!) the system!
Hardware: Dell 1950 III with Perc6i (Raid 1) with QLA2462
OS: SLES 10_SP1(64), EMCPower.LINUX.5.1.0.Patch.b194, Quantum SNFS 3.0.3.65
SAN is inactive (no zoning) only kernel modules are loaded.
Root fs is ext3
No load, nothing running on the machine. We have tested 2 different machines -> same error!
The only(!) message we get:
Aborting journal on device sda6.
ext3_abort called.
EXT3-fs error (device sda6): ext3_journal_start_sb: Detected aborted journal
Is anybody running SLES 10 SP1 on this hardware ?
Any idea what's going on ?
Yes, we have tried also news LSI driver (3.16 and 3.21)
Bye, Peer
No Events found!
SKT2
2 Intern
•
1.3K Posts
0
January 30th, 2009 11:00
Conor
341 Posts
0
February 10th, 2009 06:00
I think you have hit a known ext3 bug on SuSE10SP1... See emc180869
Ext3 bug - error handling in the ext3 filesystem code is not properly handling the case where a device has stopped to accept barrier requests, which can happen with software RAID devices, LVM devices, device-mapper devices and with third party multipathing software like EMC PowerPath.
There are two options available to correct this issue.
Contact Novell for a PTF (Program Temporary Fix) for SLES 10 SP1 and quote Novell Technical Info Document 3605538. This issue is not yet fixed in a maintenance update of the kernel.
Explicitly disable barrier support for the affected filesystems, e.g. by specifying barrier=0 in the /etc/fstab mount options field for the affected filesystems.
Refer to Novell TID# 3605538 (Technical Info Document) - http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3605538&sliceId=SAL_Public