From: Ryan Bourgeois <rgb005@latech.edu>
To: linux-ide@vger.kernel.org
Subject: Samba + SX4 + RAID5 + Ext3 = Aborted Journal
Date: Sun, 22 Aug 2004 21:10:24 -0700 [thread overview]
Message-ID: <41296E30.7050706@latech.edu> (raw)
As the subject states, I'm experiencing aborted journals on my RAID
array after large writes or a large number of writes. The strange thing
is, it only seems to happen when doing these writes from another machine
via Samba. It doesn't happen via NFS. And it only happens on the RAID
array. Here's my dmesg:
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
eth2: Setting full-duplex based on MII#1 link partner capability of 45e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 45e1.
EXT3-fs error (device md0): ext3_new_block: Allocating block in system
zone - block = 35454976
Aborting journal on device md0.
ext3_reserve_inode_write: aborting transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device md0) in
ext3_reserve_inode_write: Journal has aborted
ext3_getblk: aborting transaction: Journal has aborted in
__ext3_journal_get_create_access<3>ext3_reserve_inode_write: aborting
transaction: Journal has aborted in
__ext3_journal_get_write_access<2>EXT3-fs error (device md0) in
ext3_reserve_inode_write: Journal has aborted
ext3_abort called.
EXT3-fs abort (device md0): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device md0) in start_transaction: Journal has aborted
EXT3-fs error (device md0) in ext3_mkdir: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
I'm running the 2.6.8 kernel on both machines, but it's been happenning
since I got the array set up, which was 2.6.3 I think, but I dunno...
I'm sure an alternative filesystem would work (I think) but that poses a
data transfer problem of 120gbs...
-ryan
next reply other threads:[~2004-08-23 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 4:10 Ryan Bourgeois [this message]
2004-08-23 21:19 ` Samba + SX4 + RAID5 + Ext3 = Aborted Journal J. Ryan Earl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41296E30.7050706@latech.edu \
--to=rgb005@latech.edu \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.