All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: Martin Wilderoth <martin.wilderoth@linserv.se>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Ceph and BackupPC (was: Re: mount: 10.0.6.10:/: can't read superblock)
Date: Wed, 06 Jun 2012 15:29:05 +0200	[thread overview]
Message-ID: <3941218.dafc4yYMCO@pc10> (raw)
In-Reply-To: <c99406dc-0969-47de-a75a-72a8f42eae52@mail.linserv.se>

Am Dienstag, 5. Juni 2012, 14:33:19 schrieb Martin Wilderoth:

> I have not done any changes installed at version 0.46 upgraded earlier and
> have been testing with ceph and ceph-fuse and backuppc.

BackupPC and Ceph sounds like an interesting combination. Other than this 
hanging MDS problem, what are your experiences with that?

I'm asking because BackupPC is the only application I know of that actually 
makes heavy use of hardlinks. Ceph, as far as I've understood it, supports 
hardlinks, but works under the assumption that they're a rare and not 
performance-critical corner case, and does some optimizations that help the 
more common cases, but would probably hurt if you are using hardlinks a lot.

Regards,
	Guido

  parent reply	other threads:[~2012-06-06 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01f629d2-41bc-4266-acb7-1aeff803c38f@mail.linserv.se>
2012-06-05 18:07 ` mount: 10.0.6.10:/: can't read superblock Martin Wilderoth
2012-06-05 18:14   ` Wido den Hollander
2012-06-05 18:33     ` Martin Wilderoth
2012-06-05 20:05       ` Martin Wilderoth
2012-06-05 20:16         ` Greg Farnum
2012-06-06 13:29       ` Guido Winkelmann [this message]
2012-06-06 16:24         ` Ceph and BackupPC (was: Re: mount: 10.0.6.10:/: can't read superblock) Sage Weil
2012-06-07  8:02         ` Ceph and BackupPC Jerker Nyberg

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=3941218.dafc4yYMCO@pc10 \
    --to=guido-ceph@thisisnotatest.de \
    --cc=ceph-devel@vger.kernel.org \
    --cc=martin.wilderoth@linserv.se \
    /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.