All of lore.kernel.org
 help / color / mirror / Atom feed
* Unmountable btrfs filesystems
@ 2012-06-16 18:46 Wido den Hollander
  2012-06-16 19:12 ` Mark Nelson
  2012-06-17 13:55 ` Martin Mailand
  0 siblings, 2 replies; 6+ messages in thread
From: Wido den Hollander @ 2012-06-16 18:46 UTC (permalink / raw)
  To: ceph-devel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Unmountable btrfs filesystems
  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
  2012-06-17 13:55 ` Martin Mailand
  1 sibling, 1 reply; 6+ messages in thread
From: Mark Nelson @ 2012-06-16 19:12 UTC (permalink / raw)
  To: Wido den Hollander; +Cc: ceph-devel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Unmountable btrfs filesystems
  2012-06-16 18:46 Unmountable btrfs filesystems Wido den Hollander
  2012-06-16 19:12 ` Mark Nelson
@ 2012-06-17 13:55 ` Martin Mailand
  2012-06-18  9:30   ` Wido den Hollander
  2012-06-22 14:54   ` Guido Winkelmann
  1 sibling, 2 replies; 6+ messages in thread
From: Martin Mailand @ 2012-06-17 13:55 UTC (permalink / raw)
  To: Wido den Hollander; +Cc: ceph-devel

Hi Wido,
until recently there were still a few bugs in btrfs which could be hit 
quite easily with ceph. The last big one was fixed here 
http://www.spinics.net/lists/ceph-devel/msg06270.html

I am running a ceph cluster with btrfs on a 3.5-rc2 without a problem, 
even under heavy test load.

Hope that's helped.

-martin


Am 16.06.2012 20:46, schrieb Wido den Hollander:
> 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?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Unmountable btrfs filesystems
  2012-06-17 13:55 ` Martin Mailand
@ 2012-06-18  9:30   ` Wido den Hollander
  2012-06-22 14:54   ` Guido Winkelmann
  1 sibling, 0 replies; 6+ messages in thread
From: Wido den Hollander @ 2012-06-18  9:30 UTC (permalink / raw)
  To: martin; +Cc: ceph-devel

Hi,

On 06/17/2012 03:55 PM, Martin Mailand wrote:
> Hi Wido,
> until recently there were still a few bugs in btrfs which could be hit
> quite easily with ceph. The last big one was fixed here
> http://www.spinics.net/lists/ceph-devel/msg06270.html
>
> I am running a ceph cluster with btrfs on a 3.5-rc2 without a problem,
> even under heavy test load.
>

I'll give that one a try, thanks!

I've also let the btrfs tools like fsck loose on those filesystems, but 
they were beyond any repair. Al kinds of errors on the filesystems.

Nothing wrong with the disk below them, but the filesystems were just 
completely broken, no way of repairing.

Wido

> Hope that's helped.
>
> -martin
>
>
> Am 16.06.2012 20:46, schrieb Wido den Hollander:
>> 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?


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Unmountable btrfs filesystems
  2012-06-16 19:12 ` Mark Nelson
@ 2012-06-22 14:47   ` Guido Winkelmann
  0 siblings, 0 replies; 6+ messages in thread
From: Guido Winkelmann @ 2012-06-22 14:47 UTC (permalink / raw)
  To: Mark Nelson; +Cc: ceph-devel

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Unmountable btrfs filesystems
  2012-06-17 13:55 ` Martin Mailand
  2012-06-18  9:30   ` Wido den Hollander
@ 2012-06-22 14:54   ` Guido Winkelmann
  1 sibling, 0 replies; 6+ messages in thread
From: Guido Winkelmann @ 2012-06-22 14:54 UTC (permalink / raw)
  To: martin; +Cc: Wido den Hollander, ceph-devel

Am Sonntag, 17. Juni 2012, 15:55:42 schrieb Martin Mailand:
> Hi Wido,
> until recently there were still a few bugs in btrfs which could be hit
> quite easily with ceph. The last big one was fixed here
> http://www.spinics.net/lists/ceph-devel/msg06270.html

I keep hearing things along the lines of "yes, btrfs is really really close to 
ready, we just had some really nasty bug in the last release, so you 
absolutely have to run the very latest Linux kernel" since at least Linux 3.1.

I think I will probably wait until there have been at least three major Linux 
releases with no serious btrfs issues before I start using it in production.

	Guido

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-06-22 14:54 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2012-06-17 13:55 ` Martin Mailand
2012-06-18  9:30   ` Wido den Hollander
2012-06-22 14:54   ` Guido Winkelmann

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.