All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Wido den Hollander <wido@widodh.nl>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Unmountable btrfs filesystems
Date: Sat, 16 Jun 2012 14:12:03 -0500	[thread overview]
Message-ID: <4FDCDA83.7070708@inktank.com> (raw)
In-Reply-To: <4FDCD484.50706@widodh.nl>

On 6/16/12 1:46 PM, Wido den Hollander wrote:
> Hi,
>
> On my dev cluster (10 nodes, 40 OSD's) I'm still trying to run Ceph on
> btrfs, but over the last couple of months I've lost multiple OSD's due
> to btrfs.
>
> On my nodes I've set kernel.panic=60 so that whenever a kernel panic
> occurs I get the node back within two minutes.
>
> Now, over the last time I've seen multiple nodes reboot (didn't see the
> strace), but afterwards the btrfs filesystems on that node were
> unmountable.
>
> "btrfs: open_ctree failed"
>
> I tried various kernels, the most recent 3.3.0 from kernel.ubuntu.com,
> but I'm still seeing this.
>
> Is anyone seeing the same or did everybody migrate away to ext4 or XFS?
>
> I still prefer btrfs due to the snapshotting, but loosing all these
> OSD's all the time is getting kind of frustrating.
>
> Any thoughts or comments?
>
> Wido
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Wido,

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.

Good luck! ;)

Mark

  reply	other threads:[~2012-06-16 19:12 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 [this message]
2012-06-22 14:47   ` Guido Winkelmann
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=4FDCDA83.7070708@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=wido@widodh.nl \
    /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.