All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: Mark Nelson <mark.nelson@inktank.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Unmountable btrfs filesystems
Date: Fri, 22 Jun 2012 16:47:44 +0200	[thread overview]
Message-ID: <32695314.Vnmc9MkfxK@pc10> (raw)
In-Reply-To: <4FDCDA83.7070708@inktank.com>

Am Samstag, 16. Juni 2012, 14:12:03 schrieb Mark Nelson:
> btrfsck might tell you what's wrong.  Sounds like there is a
> btrfs-restore command in the dangerdonteveruse branch you could try.
> Beyond that, I guess it just really comes down to tradeoffs.

I've had similar problems in the recent past. Turns out Ceph makes heavy use 
of btrfs snapshots when running on btrfs, and btrfs-restore will not restore 
those, so it cannot be used to restore a broken osd.

	Guido

  reply	other threads:[~2012-06-22 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 18:46 Unmountable btrfs filesystems Wido den Hollander
2012-06-16 19:12 ` Mark Nelson
2012-06-22 14:47   ` Guido Winkelmann [this message]
2012-06-17 13:55 ` Martin Mailand
2012-06-18  9:30   ` Wido den Hollander
2012-06-22 14:54   ` Guido Winkelmann

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=32695314.Vnmc9MkfxK@pc10 \
    --to=guido-ceph@thisisnotatest.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.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.