linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux@horizon.com
To: axboe@suse.de, greg.freemyer@gmail.com, htejun@gmail.com
Cc: linux-ide@vger.kernel.org, linux@horizon.com
Subject: Re: sata_sil24 corruption details
Date: 10 Nov 2005 10:26:42 -0500	[thread overview]
Message-ID: <20051110152642.30875.qmail@science.horizon.com> (raw)
In-Reply-To: <43735C19.4040402@gmail.com>

> I'll run single drive test on sil3112 tonight, but can you please try 
> 2.6.14?  IIRC, there have been some PCI FIFO setting change.  Hmmm.. 
> oh.. it was the following commit.

I was running a post-2.6.14 libata-dev kernel, but my root file system
got corrupted, and the "emergency backup" boot image that I've
been using is 2.6.13 + libata patches.

You asked about bad block patterns...

I ran the test on three dirves at once (hdb, hdc, hdd), and the former
had no problems, while the latter two reported the following
bad blocks.  Note that these are 4096-byte block numbers relative to
a partition starting at sector 91795410.

The whole partition has 687662325 sectors, or 85957790.625 blocks.

Of those, the first pass of "badblocks -b 4096 -c 32768 -w -t random -p1"
found:

11 "bad blocks" in one pass over /dev/sdc4:
 4265401 
23598860
31564978
33854103
35258513
44588559
45069578
59358213
59554821
70448351
73983236

and 13 "bad blocks" in one pass over /dev/sdd4:
  226244  
 6595957 
 7402436 
 9464777 
14395278
14862235
15085611
16072105
16796706
26095323
39376782
46807588
51765692

It's doing a second write pass now.


It found no problems on /dev/sdb4 while there was no particular traffic on
/dev/sda.  I'm doing a run with sda and sdb in parallel.


Anyway, thanks a lot for the attention.

  reply	other threads:[~2005-11-10 15:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07  9:59 sata_sil24 corruption details linux
2005-11-07 16:15 ` Greg Freemyer
2005-11-10  7:17 ` linux
2005-11-10  9:01   ` Tejun Heo
2005-11-10 14:15     ` Greg Freemyer
2005-11-10 14:41       ` Tejun Heo
2005-11-10 15:26         ` linux [this message]
2005-11-10 17:32         ` Tejun Heo
2005-11-10 20:34           ` Greg Freemyer
2005-11-12  0:49             ` Greg Freemyer
2005-11-12  2:59               ` Tejun Heo
2005-11-13 10:19                 ` Tejun Heo
2005-11-14 23:30                   ` Greg Freemyer
2005-11-18  2:23                     ` sata_sil24 corruption FIXED by motherboard swap linux
2005-11-18 19:36                       ` sata_sil24 test support linux
2005-11-22  0:23                         ` linux
2005-11-22  1:52                           ` Tejun Heo
2005-11-11  2:16           ` sata_sil24 corruption details linux
2005-11-13  6:11             ` linux
2005-11-10 17:39         ` Jens Axboe
2005-11-10 20:27   ` Edward Falk
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 16:05 SMALL, Timothy
2005-11-15  9:30 SMALL, Timothy

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=20051110152642.30875.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=axboe@suse.de \
    --cc=greg.freemyer@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).