All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: "Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, ceph-users@lists.ceph.com
Subject: Re: Data recovery after RBD I/O error
Date: Wed, 07 Jan 2015 07:38:12 -0500	[thread overview]
Message-ID: <54AD28B4.2000802@gmail.com> (raw)
In-Reply-To: <CALJXSJpTkppvXAGb1nb5x3VFZ7CW-W9zmb3acvM=_+7SL06ixw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On 2015-01-06 23:11, Jérôme Poulin wrote:
> On Mon, Jan 5, 2015 at 6:59 AM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> Secondly, I would highly recommend not using ANY non-cluster-aware FS on top
>> of a clustered block device like RBD
>
>
> For my use-case, this is just a single server using the RBD device. No
> clustering involved on the BTRFS side of thing.
My only point is that there isn't anything in BTRFS to handle it 
accidentally being multiply mounted.  Ext* for example aren't clustered, 
but do have an optional feature to prevent multiple mounting.
> However, it was really useful to take snapshots (just like LVM) before modifying the
> filesystem in any way.
>
Have you tried Ceph's built in snapshot support?  I don't remember how 
to use it, but I do know it is there (at least, it is in the most recent 
versions), and it is a bit more like LVM's snapshots than BTRFS is.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

      reply	other threads:[~2015-01-07 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-04 20:26 Data recovery after RBD I/O error Jérôme Poulin
2015-01-05 11:59 ` Austin S Hemmelgarn
2015-01-07  4:11   ` Jérôme Poulin
2015-01-07 12:38     ` Austin S Hemmelgarn [this message]

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=54AD28B4.2000802@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=ceph-users@lists.ceph.com \
    --cc=jeromepoulin@gmail.com \
    --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 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.