From: Pavel Machek <pavel@ucw.cz>
To: jim owens <jowens@hp.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Greg Freemyer <greg.freemyer@gmail.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: Data integrity built into the storage stack
Date: Tue, 1 Sep 2009 15:37:37 +0200 [thread overview]
Message-ID: <20090901133737.GA1852@ucw.cz> (raw)
In-Reply-To: <4A9D1F0F.9050802@hp.com>
On Tue 2009-09-01 09:18:07, jim owens wrote:
> Pavel Machek wrote:
>> Hi!
>>
>>> I do agree that we do have to be more prepared for collateral damage
>>> scenarios. As we discussed at LS we have 4KB drives coming out that can
>>> invalidate previously acknowledged I/Os if it gets a subsequent write
>>> failure on a sector. And there's also the issue of fractured writes
>>
>> Hmmm, future will be interesting.
>>
>> 'ext3 expects disks to behave like disks from 1995' (alarming).
>
> NO... stop saying "ext3". All file systems expect that
> what the disk tell us is the "sector size" (now know by
> disk vendors as "block size") is "atomic".
Yep, but ext3 disables barriers by default. So it has more than
blocksize issue :-(.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2009-09-01 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 21:23 Data integrity built into the storage stack [was: Re: [testcase] test your fs/storage stack (was Re: [patch] ext2/3: document conditions when reliable operation is possible)] Greg Freemyer
2009-08-30 0:35 ` Rob Landley
2009-09-01 5:19 ` Data integrity built into the storage stack Martin K. Petersen
2009-09-01 12:44 ` Pavel Machek
2009-09-01 13:18 ` jim owens
2009-09-01 13:37 ` Pavel Machek [this message]
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=20090901133737.GA1852@ucw.cz \
--to=pavel@ucw.cz \
--cc=greg.freemyer@gmail.com \
--cc=jowens@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).