From: Tracy Reed <treed@ultraviolet.org>
To: Paul Komkoff <i@stingr.net>
Cc: Chris Mason <chris.mason@oracle.com>,
mroconnor@oel.state.nj.us, linux-btrfs@vger.kernel.org
Subject: Re: kernel bug in file-item.c
Date: Thu, 30 Apr 2009 09:54:04 -0700 [thread overview]
Message-ID: <20090430165404.GB4657@tracyreed.org> (raw)
In-Reply-To: <715ea5c10904300208l5c0ac6f1ma07f96b662304c4a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Thu, Apr 30, 2009 at 10:08:04AM +0100, Paul Komkoff spake thusly:
> On Wed, Apr 29, 2009 at 8:32 PM, Tracy Reed <treed@ultraviolet.org> wrote:
> > Note that this will be a problem that btrfs must properly manage. And
> > it must be done MUCH better than a certain previously semi-popular
> > filesystem did. The expectation needs to be set that due to the much
>
> I don't think it's workable or feasible or whatever.
> As soon as you have faulty memory or CPU, all bets are off.
Sorry, I was unclear: I meant manage in a public-relations sort of
way. Not in a technical way. You are absolutely right that bad RAM or
CPU means you are hosed.
--
Tracy Reed
http://tracyreed.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-04-30 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:39 kernel bug in file-item.c Marc R. O'Connor
2009-04-28 19:23 ` Chris Mason
2009-04-28 19:30 ` Marc R. O'Connor
2009-04-29 16:04 ` Marc R. O'Connor
2009-04-29 17:53 ` Chris Mason
2009-04-29 18:21 ` Marc R. O'Connor
2009-04-29 18:30 ` Chris Mason
2009-04-29 18:38 ` Marc R. O'Connor
2009-04-29 18:40 ` Chris Mason
2009-04-29 18:46 ` Marc R. O'Connor
2009-04-29 18:50 ` Zach Brown
2009-04-29 19:04 ` Marc R. O'Connor
2009-04-30 7:23 ` Dmitri Nikulin
2009-04-29 19:32 ` Tracy Reed
2009-04-30 9:08 ` Paul Komkoff
2009-04-30 16:54 ` Tracy Reed [this message]
2009-05-01 2:13 ` Dmitri Nikulin
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=20090430165404.GB4657@tracyreed.org \
--to=treed@ultraviolet.org \
--cc=chris.mason@oracle.com \
--cc=i@stingr.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mroconnor@oel.state.nj.us \
/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