Hi,
This happened to me also using an HP smartarray. Witch model do you have?
What I did is this:
Mark the filesystem as it does not have a journal (take it to ext2)
tune2fs -O ^has_journal /dev/cciss/c0d0p2
fsck it to delete the journal:
e2fsck /dev/cciss/c0d0p2
Create the journal (take it back to ext3)
tune2fs -j /dev/cciss/c0d0p2
and finaly, remount it. On a live system, just reboot it.
It did not happened again.
regards,
Jordi
Eric Sandeen wrote:
Mike Miller wrote:
All,
We are encountering spurious errors with ext3. After some period of heavy IO
we may see messages similiar to:
EXT3-fs error (device cciss/c0d0p5) in start_transaction: Journal has
aborted
You probably had relevant messages before that... what were they?
When this happens the filesystem is remounted read-only. If it's the root
filesystem the system becomes unresponsive and must be rebooted. An fsck on
the affected filesystem shows lots of corruption.
Any ideas on what we can do to help isolate this problem? We have 64 nodes
and the problem is random.
Crazy question, but I have to ask - you don't have the same filesystem
mounted on all those nodes, do you?
What kernel is this?
-Eric
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
--
......................................................................
__
/ / Jordi Prats
C E / S / C A Dept. de Sistemes
/_/ Centre de Supercomputació de Catalunya
Gran Capità, 2-4 (Edifici Nexus) · 08034 Barcelona
T. 93 205 6464 · F. 93 205 6979 · jprats@xxxxxxxx
......................................................................
_______________________________________________
Ext3-users mailing list
Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users
