linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evert Vorster <evorster@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Fwd: 2.6.36-rc1 btrfs still unstable
Date: Mon, 16 Aug 2010 16:11:15 +0000	[thread overview]
Message-ID: <AANLkTi=7BKfWhuRE2pQjQxM5cCVEW_L0ySUXSZnoELuo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin-q4N9g3=ymsiJy051xts3b2vioNdqku6DMEzQ@mail.gmail.com>

I thought this would go to the list automatically.

Here it is now.


---------- Forwarded message ----------
=46rom: Evert Vorster <evorster@gmail.com>
Date: Mon, Aug 16, 2010 at 4:04 PM
Subject: Re: 2.6.36-rc1 btrfs still unstable
To: Chris Ball <cjb@laptop.org>


I lost a btrfs not long ago, and this is the reason I am on this list.
Lucky for me, I have more than one backup of everything. Most people
that use computers do not. Also, they unplug USB disks without
unmounting, etc....

I don't think the signboards are big enough.

Most people assume that there is some way of fixing a broken file
system, and finding out the btrfs does not have one usually is quite
surprising and just a little too late.

I was under the impression that with atomic writes it's impossible to
mess up a file system?

-Evert-

On Mon, Aug 16, 2010 at 3:45 PM, Chris Ball <cjb@laptop.org> wrote:
> Hi,
>
> =A0 > the other big question is:
> =A0 >
> =A0 > Is btrfs with 2.6.36 really rockstable and ready to use in
> =A0 > productive environments?
>
> No, certainly not until there's a working fsck tool -- at the moment
> it's rather easy to kill a btrfs by just losing power.
>
> I just added a paragraph to the main page of the wiki about this,
> since we've had a few people on IRC express surprise that their
> filesystem aren't fixable after power loss. =A0Feel free to reword:
>
> =A0 Note that Btrfs does not yet have a fsck tool that can fix errors=
=2E
> =A0 While Btrfs is stable on a stable machine, it is currently possib=
le
> =A0 to corrupt a filesystem irrecoverably if your machine crashes or
> =A0 loses power. =A0This will be fixed when the fsck tool is ready.
>
> - Chris.
> --
> Chris Ball =A0 <cjb@laptop.org>
> One Laptop Per Child
> --
> 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 =A0http://vger.kernel.org/majordomo-info.html
>



--
http://magnatune.com - Music shared the way it should be.



--=20
http://magnatune.com - Music shared the way it should be.
--
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

  parent reply	other threads:[~2010-08-16 16:11 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         ` Evert Vorster [this message]
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
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='AANLkTi=7BKfWhuRE2pQjQxM5cCVEW_L0ySUXSZnoELuo@mail.gmail.com' \
    --to=evorster@gmail.com \
    --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).