From: Helge Hafting <helgehaf@aitel.hist.no>
To: linux-kernel@vger.kernel.org
Subject: Re: Disk (block) write strangeness
Date: Wed, 07 Aug 2002 10:14:29 +0200 [thread overview]
Message-ID: <3D50D6E5.5A81710F@aitel.hist.no> (raw)
In-Reply-To: <3D4FE0B9.751A3E92@daimi.au.dk>
Kasper Dupont wrote:
> I think it should be possible for the firmware on a good disk to
> prevent such artifacts. But I think you can find disks that just
> keeps trying to write even while power is failing.
>
That could might give you some (sub)blocks out of order, if the disk
firmware falsely believes that it is free to reorder anything
that reach its internal cache. Writing to the bitter end
will turn at least one block to garbage as write current fail
in the middle.
Alan Cox wrote:
> *) or the disk internal logic bears no resemblance to the antiquated API
> it fakes for the convenience of interface hardware and software
One may then wonder if journalling is a safe thing to do,
with out-of-order writes exposed by a power failure...
Helge Hafting
next prev parent reply other threads:[~2002-08-07 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 18:49 Jakob Oestergaard
2002-08-05 20:17 ` Alan Cox
2002-08-05 19:07 ` Jakob Oestergaard
2002-08-06 14:44 ` Kasper Dupont
2002-08-07 8:14 ` Helge Hafting [this message]
2002-08-07 11:43 ` Itai Nahshon
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=3D50D6E5.5A81710F@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--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®