From: Diego Calleja <diegocg@gmail.com>
To: Chris Ball <cjb@laptop.org>
Cc: "Morten P.D. Stevens" <mstevens@imt-systems.com>,
Chris Mason <chris.mason@oracle.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: 2.6.36-rc1 btrfs still unstable
Date: Tue, 17 Aug 2010 00:25:47 +0200 [thread overview]
Message-ID: <201008170025.47510.diegocg@gmail.com> (raw)
In-Reply-To: <m3iq3a4l46.fsf@pullcord.laptop.org>
On Lunes, 16 de Agosto de 2010 17:45:29 Chris Ball escribi=F3:
> Note that Btrfs does not yet have a fsck tool that can fix errors.
> While Btrfs is stable on a stable machine, it is currently possibl=
e
> to corrupt a filesystem irrecoverably if your machine crashes or
> loses power. This will be fixed when the fsck tool is ready.
But doesn't this happen only with cheap disks that don't honour barrier=
s
correctly?
--
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-16 22:25 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 [this message]
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
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=201008170025.47510.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mstevens@imt-systems.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 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.