public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "M.H.VanLeeuwen" <vanl@megsinet.net>
To: andre@linux-ide.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kernel require IDE enabled in BIOS to access HD, FS errors?
Date: Mon, 09 Jul 2001 07:30:19 -0500	[thread overview]
Message-ID: <3B49A3DB.A7FC143F@megsinet.net> (raw)
In-Reply-To: <3B492324.E36B86AF@linux-ide.org>

Andre,

Yes, I'd be willing to test ideas / apply any patches you'd like to try.

I was running something like this to verify corruption:

while true ; do mount /dev/hdc1 /misc ;time cp -a /usr/local/soffice52 /misc ; \
             cd /misc && md5sum --check /tmp/soffice.md5 ; cd ; umount /misc; \
             e2fsck -f -y /dev/hdc1 ; done

md5sum reported errors on the order of 28-37 corrupted files out of 576 files
copy time ~11 minutes

with dd if=/dev/zero of=/dev/null running on another terminal, 
md5sum only reported 3-8 files corrupted.
copy time ~2.5 minutes

Thanks
Martin

BTW:

here is one of the many and more verbose reports of FS corruption from e2fsck:

e2fsck 1.20, 25-May-2001 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Inode 44863, i_size is 56832, should be 3502080.  Fix? yes
 
Inode 44863, i_blocks is 120, should be 144.  Fix? yes
 
Duplicate blocks found... invoking duplicate block passes.
Pass 1B: Rescan for duplicate/bad blocks
Duplicate/bad block(s) in inode 15303: 37632
Duplicate/bad block(s) in inode 44863: 37632 113 16
Pass 1C: Scan directories for inodes with dup blocks.
Pass 1D: Reconciling duplicate blocks
(There are 2 inodes containing duplicate/bad blocks.)
 
File /office52/share/basic/template.sbl (inode #44863, mod time Mon May  8 01:20:00 2000)
  has 3 duplicate block(s), shared with 2 file(s):
        <filesystem metadata>
        /office52/share/gallery/clipart/glas.wmf (inode #15303, mod time Mon May  8 01:20:00 2000)
Clone duplicate/bad blocks? yes
 
File /office52/share/gallery/clipart/glas.wmf (inode #15303, mod time Mon May  8 01:20:00 2000)
  has 1 duplicate block(s), shared with 2 file(s):
        <filesystem metadata>
        /office52/share/basic/template.sbl (inode #44863, mod time Mon May  8 01:20:00 2000)
Duplicated blocks already reassigned or cloned.
 
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (30518, counted=30515).
Fix? yes
 
Free blocks count wrong (140220, counted=140217).
Fix? yes
 
 
/dev/hda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/hda1: 3036/104384 files (0.1% non-contiguous), 68179/208396 blocks


andre@linux-ide.org wrote:
> 
> Martin, you have an old beast that there are problems in how the chipset
> was deployed.
> How are you confirming the corruption against the various layers in the
> kernel?
> If you would like patches & tests to verify I will send them to you.
> 
> Cheers
> 
> --
> Andre Hedrick
> Linux ATA Development
> ASL Kernel Development
> -----------------------------------------------------------------------------
> ASL, Inc.                                     Toll free: 1-877-ASL-3535
> 1757 Houret Court                             Fax: 1-408-941-2071
> Milpitas, CA 95035                            Web: www.aslab.com

  reply	other threads:[~2001-07-09 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09  3:21 Does kernel require IDE enabled in BIOS to access HD, FS errors? andre
2001-07-09 12:30 ` M.H.VanLeeuwen [this message]
2001-07-10  3:41 ` M.H.VanLeeuwen
2001-07-10  6:37   ` Andre Hedrick
  -- strict thread matches above, loose matches on Subject: below --
2001-07-08 14:41 Adam Kropelin
2001-07-07  5:25 M.H.VanLeeuwen
2001-07-07 13:18 ` Jim Roland
2001-07-07 13:47   ` M.H.VanLeeuwen
2001-07-07 20:42     ` Jim Roland
2001-07-07 20:50       ` Rik van Riel

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=3B49A3DB.A7FC143F@megsinet.net \
    --to=vanl@megsinet.net \
    --cc=andre@linux-ide.org \
    --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