From: Xavier Nicollet <nicollet@jeru.org>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: 2.6.36-rc1 btrfs still unstable
Date: Thu, 26 Aug 2010 10:58:01 +0200 [thread overview]
Message-ID: <20100826085801.GQ1344@jeru.org> (raw)
In-Reply-To: <201008251857.39585.johannes.hirte@fem.tu-ilmenau.de>
Le 25 ao=FBt 2010 =E0 18:57, Johannes Hirte a =E9crit:
> > the other big question is:
> > Is btrfs with 2.6.36 really rockstable and ready to use in producti=
ve environments?
>=20
> I don't think so. There is at least one checksum bug and ENOSPC probl=
ems are also still present.
I am planning to put 2 dedicated web hosting servers in production
(backuped every day), with 2.6.34.5 vanilla kernel.
I also use btrfs on a 2.6.34 kernel on the backup server (rsync) for
some time.
--=20
Xavier Nicollet
--
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-08-26 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 8:46 2.6.36-rc1 btrfs still unstable Ameya Palande
2010-08-16 12:16 ` Chris Mason
2010-08-16 14:17 ` Morten P.D. Stevens
2010-08-16 15:45 ` Chris Ball
[not found] ` <AANLkTin-q4N9g3=ymsiJy051xts3b2vioNdqku6DMEzQ@mail.gmail.com>
2010-08-16 16:11 ` Fwd: " Evert Vorster
2010-08-16 16:32 ` Chris Ball
2010-08-16 22:25 ` Diego Calleja
2010-08-26 22:45 ` Roy Sigurd Karlsbakk
2010-08-26 23:17 ` Diego Calleja
2010-08-17 11:57 ` Carlos R. Mafra
2010-08-17 16:25 ` Rodrigo E. De León Plicet
2010-08-25 16:57 ` Johannes Hirte
2010-08-26 8:58 ` Xavier Nicollet [this message]
2010-08-26 22:48 ` Roy Sigurd Karlsbakk
2010-08-17 0:14 ` Chris Samuel
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=20100826085801.GQ1344@jeru.org \
--to=nicollet@jeru.org \
--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 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.