mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samium Gromoff <_deepfire@mail.ru>
To: barryn@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Howl of soul...
Date: Wed, 26 Sep 2001 03:01:38 +0000 (UTC)	[thread overview]
Message-ID: <200109260301.f8Q31cq06972@vegae.deep.net> (raw)

>  A low-level format (using IBM DFT) is going to *silently* remap bad
>  parts of the disk. It's only going to complain once it's no longer
>  possible to remap the bad sectors. So, just because the low-level format
>  doesn't complain does not mean that there is no media degradation!
    1. how to find problematic blocks?
           - just read, and if read fails goto 2.
	     (i.e. we found no new bad sectors)
	   - goto 2 on the sectors reported before as bad.
             (i.e. drive remembers sectors on which he had failures)
    2. what to do when i found problematic sector?
           - just see if it still usable.
         2a. i write to the sector, and after that i read crap.
               - sector is bad! should remap it!
         2b. i can write data to the sector, then reads goes ok.
               - hmm, i think that was kinda magnetetic storm, sector
 is still usable. do not remapping.

        in my case there was just magnetic storm, so the sector can be safely
     read/written again.

cheers,
Sam


             reply	other threads:[~2001-08-26 22:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26  3:01 Samium Gromoff [this message]
2001-08-29 20:30 ` Pavel Zaitsev
  -- strict thread matches above, loose matches on Subject: below --
2001-08-26 12:13 Samium Gromoff
2001-08-25 20:11 Samium Gromoff
2001-08-26 22:06 ` Barry K. Nathan
2001-09-07 16:12   ` Marco Colombo
2001-08-25 12:41 Samium Gromoff
2001-08-24 16:40 Samium Gromoff
2001-08-24 18:33 ` Justin Guyett
2001-08-24 20:00   ` Alan Cox
2001-08-24 20:08     ` David Huen
2001-08-24 20:34     ` Paul Jakma
2001-08-25  1:26     ` Mike Castle
2001-08-26 11:41 ` Hans Reiser

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=200109260301.f8Q31cq06972@vegae.deep.net \
    --to=_deepfire@mail.ru \
    --cc=barryn@pobox.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

all inboxes | Powered by JetHome®