From: Peter DeVries <peter@devries.tv>
To: linux-kernel@vger.kernel.org
Subject: Progress with drive corruption with KT7-RAID.
Date: Thu, 08 Mar 2001 18:08:15 -0500 [thread overview]
Message-ID: <3AA810DF.3070809@devries.tv> (raw)
[-- Attachment #1: Type: text/plain, Size: 306 bytes --]
When I put the HD on ide2 and do the appropriate changes (ide=reverse)
The systemn is more stable. I am getting the following message when
moving data around. There seems to be a little corruption of the
directory stucture, Specifically in /usr/src/linux which I just used to
compile the kernel.
[-- Attachment #2: error-dma-2.4.2-ac12 --]
[-- Type: text/plain, Size: 441 bytes --]
Config - 2.4.2-ac12, 20g IBM drive UDMA33, HD on Highpoint controller,
UDMA100, ide2
EXT2-fs error (device ide0(3,10)): ext2_readdir: bad entry in directory #32447:
rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
cp: /usr/src/linux/ipc/util.c: Input/output error
cp: /usr/src/linux/ipc/Makefile: Input/output error
cp: /usr/src/linux/ipc/util.h: Input/output error
cp: /usr/src/linux/drivers: Input/output error
reply other threads:[~2001-03-08 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3AA810DF.3070809@devries.tv \
--to=peter@devries.tv \
--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