From: Francis Galiegue <fgaliegue@gmail.com>
To: "K. Richard Pixley" <rich@noir.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Francis Galiegue would like your help testing a survey
Date: Tue, 28 Sep 2010 20:47:14 +0200 [thread overview]
Message-ID: <AANLkTikoYwSkVyTqX1LLLzCDp_nELVxm7WqJa1ffqkZb@mail.gmail.com> (raw)
In-Reply-To: <4CA2092A.8020207@noir.com>
[cc: list]
On Tue, Sep 28, 2010 at 17:26, K. Richard Pixley <rich@noir.com> wrote:
> =C2=A0#2 needs an answer dealing with "stability". =C2=A0Unstable doe=
sn't necessarily
> mean polluted file systems. =C2=A0It can also mean pathological behav=
ior, kernel
> crashes, etc.
>
Yes, indeed. Fixed.
> #4 needs an answer that involves performance - btrfs is, (arguably), =
the
> fastest file system currently available for linux in many situations.=
=C2=A0That
> answer alone is a serious selling point.
>
> Another selling point for #4 is file system hardening. =C2=A0ext2 is =
still fast,
> but it can't generally survive power failures. =C2=A0If you're specif=
ically
> looking for a fast file system, then the fact that btrfs competes wel=
l in
> speed and is also hardened becomes a selling point.
>
Well, performance is not touted as a key feature on the btrfs wiki. I
have added "good overall performance" in the list of choices, though.
As to file system hardening, what do you mean apart from checksums?
=46undamental filesystem design?
> #15 presupposes it's own answer. =C2=A0While I've had no filesystems =
fail, every
> machine I use with btrfs file systems has failed numerous times -
> pathological behavior, kernel crashes, etc. =C2=A0In the absence of a=
btrfsck I
> can't be sure that the file system has actually failed although rebui=
lding
> the file system seems to alleviate the symptoms temporarily.
>
I don't really see your point here. Can you elaborate? And yes, I _do_
mean filesystem failures, not machine failure. I made that explicit.
> #16 presupposes a failure mode.=C2=A0Again, my issues have more to do=
with
> stability than with clear cases of file system pollution.
>
Point taken, but again, this is on purpose, I talk here about hosed
filesystems indeed.
Thanks for the feedback!
--=20
=46rancis Galiegue, fgaliegue@gmail.com
"It seems obvious [...] that at least some 'business intelligence'
tools invest so much intelligence on the business side that they have
nothing left for generating SQL queries" (St=C3=A9phane Faroult, in "Th=
e
Art of SQL", ISBN 0-596-00894-5)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-09-28 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:27 Francis Galiegue would like your help testing a survey Francis Galiegue
2010-09-28 14:57 ` David Pottage
2010-09-28 15:07 ` Francis Galiegue
2010-09-28 17:48 ` Freddie Cash
2010-09-28 18:50 ` Francis Galiegue
[not found] ` <4CA2092A.8020207@noir.com>
2010-09-28 18:47 ` Francis Galiegue [this message]
2010-09-29 15:11 ` K. Richard Pixley
2010-09-28 19:00 ` Francis Galiegue
2010-09-28 19:18 ` Andreas Philipp
2010-09-28 19:23 ` Francis Galiegue
2010-09-28 19:27 ` cwillu
2010-09-28 19:49 ` Francis Galiegue
2010-09-28 22:00 ` Kristian Lyngstol
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=AANLkTikoYwSkVyTqX1LLLzCDp_nELVxm7WqJa1ffqkZb@mail.gmail.com \
--to=fgaliegue@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rich@noir.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).