public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Vipin Malik <vmalik@danielind.com>
To: MTD <mtd@imladris.mvhi.com>
Subject: [Fwd: Power Down]
Date: Wed, 08 Dec 1999 15:39:23 -0600	[thread overview]
Message-ID: <384ED00B.F678D296@danielind.com> (raw)

David Woodhouse wrote:
> 
> rcanup@go2fax.com said:
> >  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.
> 
> At the block device level, that definitely shouldn't occur. The ext2 may of
> course get confused, but that's why you should be using ext3 on it if you ever
> expect it to lose power.

I can gurantee you that it did with at least 3 or 4 IDE2000 disks that I
tested. Also with a couple of compact flash disks that I tested. The
compact flash were so bad (1 in about 4 problems on power downs) that I
just gave up on those as completely unacceptable.

> 
> > 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.
> 
> With NFTL, that's definitely the way it's designed. You write the data, write
> the ECC checksum, and then mark it valid. The old version of that block remains
> on the media until it's later reclaimed.
> 
> If you are interrupted during a write, it's obvious and can be fixed.

Is this functionality already there in the drivers on the web site. Has
this been tested during power downs during writes to flash?


> 
> --
> dwmw2
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~1999-12-08 21:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-08 21:39 Vipin Malik [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-08 21:36 [Fwd: Power Down] Vipin Malik
1999-12-08 23:02 ` Bob Canup
1999-12-09 11:02   ` David Woodhouse
1999-12-09 14:56   ` Bob Canup
1999-12-20  4:22     ` Stuart Lynne
1999-12-08 21:32 Vipin Malik
1999-12-09 11:10 ` David Woodhouse
1999-12-08 20:48 Vipin Malik
1999-12-08 20:42 Vipin Malik
1999-12-07 16:36 [Fwd: power down] Oron Ogdan
1999-12-06 23:41 Vipin Malik
1999-12-07 15:47 ` Bob Canup
1999-12-20  4:03   ` Stuart Lynne
1999-12-07 20:36 ` Jon Burford
1999-12-13 14:49   ` Adi Linden
1999-12-13 19:07     ` Jon Burford
1999-12-08 15:10 ` David Woodhouse

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=384ED00B.F678D296@danielind.com \
    --to=vmalik@danielind.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