linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tetja Rediske <tetja@tetja.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid5 unmountable
Date: Tue, 4 Feb 2014 10:31:05 +0100	[thread overview]
Message-ID: <20140204103105.16d09394@trediske.ws.office.manitu.net> (raw)

Hello Duncan,

> Of course if you'd been following the list as btrfs testers really
> should still be doing at this point, you'd have seen all this covered
> before. And of course, if you had done pre-deployment testing before
> you stuck valuable data on that btrfs raid5, you'd have noted the
> problems, even without reading about it on-list or on the wiki.  But
> of course hindsight is 20/20, as they say, and at least you DO have
> backups, even if they'll take awhile to restore.  =:^) That's already
> vastly better than a lot of the reports we unfortunately get here.
> =:^\

yeah, i saw it. Main reason for me "toying" with btrfs is my work. We
rent Linux servers to customers. While they install and manage them by
them self, there will be questions about btrfs to our support, sooner or
later. So getting your hands on it early saves some headache later.

It is just inconvient for me now, so no big deal.

I first tried degraded, I also tried repair, no luck.

What I do now is, getting as much data from the broken fs with btrfs
recover and do a rsync after. It is just faster then downloading all
the data from my own mirror in the datacenter. ;)

After that I will even be so crazy and try it again. Next on my list is
send/receive. 

Tetja




             reply	other threads:[~2014-02-04  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04  9:31 Tetja Rediske [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-03 16:12 btrfs raid5 unmountable Tetja Rediske
2014-02-04  6:08 ` Duncan

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=20140204103105.16d09394@trediske.ws.office.manitu.net \
    --to=tetja@tetja.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).