From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Cc: sct@redhat.com, akpm@digeo.com, adilger@clusterfs.com
Subject: ext3 error with 2.6.9-rc4
Date: Wed, 13 Oct 2004 00:29:43 +1000 [thread overview]
Message-ID: <20041012142943.GD920@zip.com.au> (raw)
The fs is on a 200gb seagate hd on a promise pci card (20267 - latest
firmware). It's hdh1. I was tarring a fs on hde1 onto hdh1. It ran for a
bit and then stopped with my kern.log providing the following error:
Oct 13 00:12:03 nessie kernel: EXT3-fs: mounted filesystem with ordered data mode.
Oct 13 00:17:03 nessie kernel: EXT3-fs error (device hdh1): ext3_readdir: bad entry in directory #3522561: rec_len is smaller than minimal - offset=4084, inode=3523431, rec_len=0, name_len=0
Oct 13 00:17:03 nessie kernel: Aborting journal on device hdh1.
Oct 13 00:17:03 nessie kernel: ext3_abort called.
Oct 13 00:17:03 nessie kernel: EXT3-fs error (device hdh1): ext3_journal_start: Detected aborted journal
Oct 13 00:17:03 nessie kernel: Remounting filesystem read-only
Oct 13 00:17:03 nessie kernel: EXT3-fs error (device hdh1) in start_transaction: Journal has aborted
Oct 13 00:17:58 nessie kernel: __journal_remove_journal_head: freeing b_committed_data
A similarish error occured under 2.6.8-rc2:
Sep 19 07:39:29 nessie kernel: attempt to access beyond end of device
Sep 19 07:39:29 nessie kernel: hdh1: rw=1, want=3186822344, limit=390716802
Sep 19 07:39:29 nessie kernel: Aborting journal on device hdh1.
Sep 19 07:39:29 nessie kernel: ext3_abort called.
Sep 19 07:39:29 nessie kernel: EXT3-fs abort (device hdh1): ext3_journal_start: Detected aborted journal
Sep 19 07:39:29 nessie kernel: Remounting filesystem read-only
Sep 19 07:39:29 nessie kernel: EXT3-fs error (device hdh1) in
start_transaction: Journal has aborted
This was during a copy from hde2 to hdh1. 2.6.9-rc4 survived this bit
but died anyway when more data was written to the fs when tarring.
The HD is brand new.
Any help I can provide in helping debug this I will gladly give. Just
give me a shout.
--
Red herrings strewn hither and yon.
next reply other threads:[~2004-10-12 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 14:29 CaT [this message]
2004-10-14 16:51 ` ext3 error with 2.6.9-rc4 Stephen C. Tweedie
2004-10-30 3:52 ` CaT
[not found] <fa.cbe1dra.16ke3gi@ifi.uio.no>
2004-10-14 4:12 ` Robert Hancock
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=20041012142943.GD920@zip.com.au \
--to=cat@zip.com.au \
--cc=adilger@clusterfs.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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.