From: rwhron@earthlink.net
To: linux-kernel@vger.kernel.org
Subject: Re: ext3 badness in 2.6.0-test2
Date: Wed, 6 Aug 2003 02:40:26 -0400 [thread overview]
Message-ID: <20030806064026.GA1084@rushmore> (raw)
>> EXT3-fs error (device md0) in start_transaction: Journal has aborted
> Without the initial message we do not know.
During a dbench 64 run with 2.6.0-test2-mm4 on ext3 /var/log/messages said:
kernel: attempt to access beyond end of device
kernel: hdc1: rw=0, want=1212696656, limit=4096449
fdisk /dev/hdc using sectors for units shows:
Disk /dev/hdc: 16 heads, 63 sectors, 39703 cylinders
Units = sectors of 1 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 63 4096511 2048224+ 83 Linux
/dev/hdc2 4096512 23634575 9769032 83 Linux
/dev/hdc3 * 23634576 40020623 8193024 83 Linux
The console displayed:
Buffer I/O error on device hdc1, logical block 298266
lost page write due to I/O error on hdc1
Buffer I/O error on device hdc1, logical block 298112
lost page write due to I/O error on hdc1
Buffer I/O error on device hdc1, logical block 296626
lost page write due to I/O error on hdc1
Buffer I/O error on device hdc1, logical block 294743
lost page write due to I/O error on hdc1
EXT3-fs error (device hdc1): ext3_free_blocks: Freeing blocks not in datazone - block = 151587081, count = 1
Aborting journal on device hdc1.
ext3_abort called.
EXT3-fs abort (device hdc1): ext3_journal_start: Detected aborted journal
Remounting filesystem read-only
ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdc1) in ext3_truncate: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdc1) in ext3_orphan_del: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device hdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdc1) in ext3_delete_inode: Journal has aborted
The console did not respond to <Enter>.
The machine was pingable, but would not give an ssh prompt.
Additional /var/log/messages:
Aug 5 20:29:24 mountain kernel: Buffer I/O error on device hdc1, logical block 298266
Aug 5 20:29:24 mountain kernel: lost page write due to I/O error on hdc1
Aug 5 20:29:24 mountain kernel: Buffer I/O error on device hdc1, logical block 298112
Aug 5 20:29:24 mountain kernel: lost page write due to I/O error on hdc1
Aug 5 20:29:24 mountain kernel: Buffer I/O error on device hdc1, logical block 296626
Aug 5 20:29:24 mountain kernel: lost page write due to I/O error on hdc1
Aug 5 20:29:24 mountain kernel: Buffer I/O error on device hdc1, logical block 294743
Aug 5 20:29:24 mountain kernel: lost page write due to I/O error on hdc1
Aug 5 20:29:24 mountain kernel: attempt to access beyond end of device
Aug 5 20:29:24 mountain kernel: hdc1: rw=0, want=1212696656, limit=4096449
Aug 5 20:29:24 mountain kernel: attempt to access beyond end of device
Aug 5 20:29:24 mountain kernel: hdc1: rw=0, want=1212696656, limit=4096449
Aug 5 20:29:24 mountain kernel: attempt to access beyond end of device
Aug 5 20:29:36 mountain kernel: hdc1: rw=0, want=1212696656, limit=4096449
..
Uniprocessor K6/2 with IDE disks.
It did not have a problem with dbench 32 on ext3.
dbench on ext2 ran fine too.
e2fsprogs-1.33. After e2fsck, filesystem seems okay.
--
Randy Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2003-08-06 6:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 6:40 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 14:22 ext3 badness in 2.6.0-test2 Daniel Jacobowitz
2003-08-04 20:22 ` Andrew Morton
2003-08-06 6:36 ` Neil Brown
2003-08-06 6:57 ` Andrew Morton
2003-08-08 1:00 ` Neil Brown
2003-08-08 1:16 ` Andrew Morton
2003-08-09 0:39 ` Neil Brown
2003-08-09 1:05 ` Mike Fedyk
2003-08-10 23:44 ` Neil Brown
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=20030806064026.GA1084@rushmore \
--to=rwhron@earthlink.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox