From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: C Anthony Risinger <anthony@extof.me>
Cc: Hendrik Fabelje <hendrik@fabelje.de>, linux-btrfs@vger.kernel.org
Subject: Re: Question of stability
Date: Sun, 19 Sep 2010 04:00:37 +0200 (CEST) [thread overview]
Message-ID: <19323412.131.1284861637528.JavaMail.root@zimbra> (raw)
In-Reply-To: <-2391411343414296963@unknownmsgid>
> Stable is a pretty subjective term; many don't even think ext4 is
> stable. I've used it on my personal machine since .30-31-ish without
> problems, and on a server w/raid 1 for about a year (btrfs + lxc is
> niiice, for VMs) also free of problems.
>=20
> However, if you've been on the list you know that some do encounter
> seemingly catastrophic problems, though the list is helpful in
> recovering data. So, it's really going to depends on your workload
> and integrity needs. I remeber someone recently using it for
> continuous build servers successfully
The term stable may be subjective at times, but for btrfs to be stable,=
it needs a working filesystem, with offline or online fsck abilities, =
and allowing for what's in the idea of btrfs, that is, checksumming eve=
rything, allowing snapshots and rollbacks et cetera. If btrfs is only s=
table as in ext4, well, why not just use ext4? The whole reason for btr=
fs to exist is to bring something new into the Linux world, and if thos=
e features aren't stable, then btrfs isn't. It's as simple as that. Wou=
ld you buy a Subaru (or something) 4wd with a 2wd working?
Vennlige hilsener / Best regards
roy
--
Roy Sigurd Karlsbakk
(+47) 97542685
roy@karlsbakk.net
http://blogg.karlsbakk.net/
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt.=
Det er et element=C3=A6rt imperativ for alle pedagoger =C3=A5 unng=C3=A5=
eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste ti=
lfeller eksisterer adekvate og relevante synonymer p=C3=A5 norsk.
--
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-19 2:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 21:37 Question of stability Roy Sigurd Karlsbakk
2010-09-18 21:55 ` Hendrik Fabelje
2010-09-18 23:55 ` Roy Sigurd Karlsbakk
2010-09-19 0:43 ` C Anthony Risinger
2010-09-19 2:00 ` Roy Sigurd Karlsbakk [this message]
2010-09-19 4:50 ` C Anthony Risinger
2010-09-20 15:12 ` K. Richard Pixley
2010-09-20 15:27 ` C Anthony Risinger
2010-09-19 9:51 ` Hugo Mills
2010-09-20 1:18 ` Chris Samuel
2010-09-20 11:00 ` Lubos Kolouch
2010-09-20 11:30 ` Chris Mason
2010-09-20 12:10 ` Lubos Kolouch
2010-09-20 12:13 ` Chris Mason
2010-09-22 14:04 ` Lubos Kolouch
2010-09-22 22:50 ` Chris Mason
2010-09-20 12:21 ` Stephan von Krawczynski
2010-09-20 12:27 ` Chris Mason
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=19323412.131.1284861637528.JavaMail.root@zimbra \
--to=roy@karlsbakk.net \
--cc=anthony@extof.me \
--cc=hendrik@fabelje.de \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).