From: <jscottkasten@yahoo.com>
To: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>,
"Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: Valdis.Kletnieks@vt.edu, Pavel Machek <pavel@ucw.cz>,
J Engel <joern@wohnheim.fh-wedel.de>,
Peter Menzebach <pm-mtd@mw-itcon.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: data loss on jffs2 filesystem on dataflash
Date: Thu, 22 Sep 2005 11:43:24 -0700 (PDT) [thread overview]
Message-ID: <20050922184324.235.qmail@web34409.mail.mud.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0509221306350.4631@chaos.analogic.com>
Actually, 3 years ago, I researched this in my
company's lab. There is about a 1 in 180 probability
of the power to the read/write head failing before the
sector write is complete.
The end result is a sector that fails ECC check. The
linux kernel reports this and your I/O operation
returns with an error.
Not easy, but if you force a rewrite of the sector,
the problem cures itself. Not easy to do through the
VFS though. I was only able to make it happen by
using dd if=/dev/zero on the unmounted device node.
After that, the sector read just fine.
-Scott Kasten-
--- "linux-os (Dick Johnson)" <linux-os@analogic.com>
wrote:
>
> On Thu, 22 Sep 2005, Artem B. Bityutskiy wrote:
>
> > Valdis.Kletnieks@vt.edu wrote:
> >> On Thu, 22 Sep 2005 14:48:39 +0400, "Artem B.
> Bityutskiy" said:
> >>
> >>> Joern meant that if HDD starts a block write
> operation, it will
> >>> accomplish it even if power-fail happens
> (probably there are some
> >>> capacitors there). So, it is impossible, say,
> that HDD has written one
> >>> half of a sector and has not written the other
> half.
> >>
> >> Hard drives contain capacitors to prevent writing
> of runt sectors on
> >> a powerfail? Didn't we go around this a while
> ago and decide it's mostly
> >> urban legend, and that plenty of people have seen
> runt/bad sectors?
> >
> > No idea. But theoretically it should be so, at
> least "good" drives
> > should. May be a competent person will comment on
> this, that's quite
> > interesting.
> >
> > --
> > Best Regards,
> > Artem B. Bityuckiy,
> > St.-Petersburg, Russia.
>
> The only significant energy storage that hard disks
> contain
> is the inertia of the rotating disk assembly. Since
> the platter
> motor is not a generator it doesn't help. Those tiny
> bypass
> capacitors you see can't store enough energy to do
> anything
> useful during a power failure.
>
> BUT... The PC/AT power supplies store a lot of
> energy and
> they run for many milliseconds after a power fail.
> 2-100 uF in series = 50 uF @ 300 v.
> J = 1/2 CV^2
>
> J = 50uF * 300^2 / 2 = 2.25 joules (lots of
> energy).
>
> If the power-fail line is properly connected and if
> the
> power fail line operates at the correct time, the
> CPU
> will be halted while there is still enough energy
> available
> to complete any write that has gotten to the
> disk-drives sector
> buffer. This does not protect data, but it should
> certainly
> protect the sectors which might now contain header,
> good data
> or junk, and a proper CRC. IOW a good sector.
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.13 on an i686 machine
> (5589.55 BogoMips).
> Warning : 98.36% of all statistics are fiction.
>
>
****************************************************************
> The information transmitted in this message is
> confidential and may be privileged. Any review,
> retransmission, dissemination, or other use of this
> information by persons or entities other than the
> intended recipient is prohibited. If you are not
> the intended recipient, please notify Analogic
> Corporation immediately - by replying to this
> message or by sending an email to
> DeliveryErrors@analogic.com - and destroy all copies
> of this information, including any attachments,
> without reading or disclosing them.
>
> Thank you.
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-09-22 18:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <432812E8.2030807@mw-itcon.de>
[not found] ` <432817FF.10307@yandex.ru>
[not found] ` <4329251C.7050102@mw-itcon.de>
[not found] ` <4329288B.8050909@yandex.ru>
[not found] ` <43292AC6.40809@mw-itcon.de>
[not found] ` <43292E16.70401@yandex.ru>
[not found] ` <43292F91.9010302@mw-itcon.de>
[not found] ` <432FE1EF.9000807@yandex.ru>
[not found] ` <432FEF55.5090700@mw-itcon.de>
2005-09-20 12:55 ` Artem B. Bityutskiy
2005-09-20 13:32 ` Jörn Engel
2005-09-20 14:11 ` Artem B. Bityutskiy
2005-09-21 19:07 ` Pavel Machek
2005-09-22 10:48 ` Artem B. Bityutskiy
2005-09-22 16:46 ` Valdis.Kletnieks
2005-09-22 17:03 ` Artem B. Bityutskiy
2005-09-22 17:22 ` linux-os (Dick Johnson)
2005-09-22 18:43 ` jscottkasten [this message]
2005-09-23 8:51 ` Jörn Engel
2005-09-22 11:34 ` Jörn Engel
2005-09-22 11:54 ` Jörn Engel
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=20050922184324.235.qmail@web34409.mail.mud.yahoo.com \
--to=jscottkasten@yahoo.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dedekind@yandex.ru \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=pavel@ucw.cz \
--cc=pm-mtd@mw-itcon.de \
/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®