From: Bob Canup <rcanup@go2fax.com>
To: MTD <mtd@imladris.mvhi.com>
Subject: Re: Power Down
Date: Wed, 08 Dec 1999 08:55:12 -0600 [thread overview]
Message-ID: <384E7150.F31E542C@go2fax.com> (raw)
It is obvious that a physical medium such as a disk is vulnerable to
having a bad sector created by the process that I described. The proof
is simple: pop out a diskette while you are writing to it and you stand
a good chance of creating a sector in which the CRC and data are out of
sync. When you attempt to read the sector you will get a bad CRC.
This occurs in a diskette because the writing process is a serial event;
it is spread over time. So there is a window in which an interruption
can create a bad sector.
Let us assume the the DOC writes all of the bytes in a page including
the ECC code in parallel, let us also assume that you have an internal
bit which marks a sector as good when that process has completed. There
nevertheless is a time during the 'burn' of the bits where we are in an
analog state of changing the bits. If power is lost at that time - some
of the bits will not have changed to their proper state. Even if the
page is not marked as good an attempt to read the page will result in an
ECC and data which do not match and the result is a bad sector. The
sector may be easily recovered by erasing it and starting over - but as
long as there is an analog aspect to changing the states - the bits will
not all change at the same instant and a window for corruption exists.
Vipin's original post said that he saw bad sectors about once in every
250 power down cycles. Oran is telling us that can't occur.
Of course if my analysis is correct then you are safe to erase the bad
sector - it was the last one being written; the file system would then
be left in a state in which e2fsck could hopefully repair it.
Or am I off in left field with this?
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~1999-12-08 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-08 14:55 Bob Canup [this message]
1999-12-08 15:04 ` Power Down David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
1999-12-08 8:57 Oron Ogdan
1999-12-08 0:58 Oron Ogdan
1999-12-08 9:54 ` David Woodhouse
1999-12-10 10:41 ` Stephen C. Tweedie
1999-12-03 19:28 power down Bob Canup
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=384E7150.F31E542C@go2fax.com \
--to=rcanup@go2fax.com \
--cc=mtd@imladris.mvhi.com \
/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