From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Integrity and corruption - can file systems be scalable?
Date: Fri, 2 Jul 2010 16:09:47 -0500 [thread overview]
Message-ID: <20100702210947.GF15407@oracle.com> (raw)
In-Reply-To: <AANLkTim773u3UsE0zo0T-a6nzTkqKiv0qxByxx918vgY@mail.gmail.com>
On Fri, Jul 02, 2010 at 02:59:00PM -0600, Peter Braam wrote:
> The point of the note is the opposite of what you write, namely that backend
> systems in fact do not solve this, unless they are guaranteed to be bug
> free.
Fsck tools can also be buggy. Consider them redundant code run
asynchronously. Is it possible to fsck petabytes in reasonable time?
Not if storage capacity grows faster than storage bandwidth.
The obvious alternatives are: test, test, test, and/or run redundant
fsck-like code synchronously. The latter could be done by reading
just-written transactions to check that the filesystem is consistent.
Nico
--
next prev parent reply other threads:[~2010-07-02 21:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 18:53 [Lustre-devel] Integrity and corruption - can file systems be scalable? Peter Braam
2010-07-02 20:52 ` Dmitry Zogin
2010-07-02 20:59 ` Peter Braam
2010-07-02 21:09 ` Nicolas Williams [this message]
2010-07-02 21:18 ` Dmitry Zogin
2010-07-02 21:39 ` Peter Braam
2010-07-02 22:21 ` Nicolas Williams
2010-07-02 22:35 ` Nicolas Williams
2010-07-03 3:37 ` Dmitry Zogin
2010-07-04 23:56 ` Nicolas Williams
2010-07-05 3:53 ` Dmitry Zogin
2010-07-05 7:11 ` Mitchell Erblich
2010-07-05 17:58 ` Nicolas Williams
2010-07-07 6:57 ` [Lustre-devel] [Lustre-discuss] " Andreas Dilger
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=20100702210947.GF15407@oracle.com \
--to=nicolas.williams@oracle.com \
--cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.