From: Mike Fedyk <mfedyk@matchmail.com>
To: davidge@jazzfree.com
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Some ext2 errors
Date: Sat, 6 Oct 2001 12:13:22 -0700 [thread overview]
Message-ID: <20011006121322.B2625@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0110061713130.485-100000@fargo>
In-Reply-To: <Pine.LNX.4.33.0110061713130.485-100000@fargo>
On Sat, Oct 06, 2001 at 05:15:22PM +0200, davidge@jazzfree.com wrote:
>
> Hi,
>
> First i thought this errors has some relation with kernel 2.4.10 and
> e2fsprogs, but i switched back to 2.4.9 and again i got this
> ext2_check_page error.
>
> Oct 6 17:11:08 fargo kernel: EXT2-fs error (device ide0(3,1)):
> ext2_check_page: bad entry in directory #423505: unaligned directory entry
> - offset=0, inode=6517874, rec_len=12655, name_len=48
This error caused by below error...
> Oct 6 17:11:08 fargo kernel: hda: status error: status=0x58 { DriveReady
> SeekComplete DataRequest }
I've only seen this myself when I've been messing with hdparm on a ide drive
> Oct 6 17:11:08 fargo kernel: hda: drive not ready for command
> Oct 6 17:11:08 fargo kernel: hdb: ATAPI DVD-ROM drive, 512kB Cache
> Oct 6 17:11:08 fargo kernel: Uniform CD-ROM driver Revision: 3.12
> Oct 6 17:11:09 fargo kernel: VFS: Disk change detected on device
> ide0(3,64)
>
>
> Any hints are welcome, thanks.
>
Yeah. If you can't figure out hdparm, leave it alone.
>
> David G?mez
>
Mike
next prev parent reply other threads:[~2001-10-06 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 15:15 Some ext2 errors davidge
2001-10-06 19:13 ` Mike Fedyk [this message]
2001-10-06 23:05 ` Riley Williams
2001-10-07 13:15 ` David Gómez
2001-10-07 18:02 ` IDE DMA errors [was: Some ext2 errors] Mike Fedyk
2001-10-07 22:39 ` Riley Williams
2001-10-08 0:32 ` Mike Fedyk
2001-10-08 0:51 ` David Gómez
2001-10-08 11:19 ` Riley Williams
2001-10-08 18:24 ` David Gómez
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=20011006121322.B2625@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=davidge@jazzfree.com \
--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