All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Pirl <btrfs@lukas-pirl.de>
To: Duncan <1i5t5.duncan@cox.net>, hugo@carfax.org.uk, ahferroin7@gmail.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: corrupted RAID1: unsuccessful recovery / help needed
Date: Sun, 8 Nov 2015 15:59:05 +1300	[thread overview]
Message-ID: <563EBA79.6040808@lukas-pirl.de> (raw)
In-Reply-To: <pan$2c57b$16ebecd2$7cec1c09$cc5ded39@cox.net>

Thanks for the answers Duncan, Hugo and Austin.

I'll try a recovery as soon as I can and might (probably) come back to
the list then.

On 10/30/2015 11:58 PM, Duncan wrote:
> Meanwhile, this does reinforce the point that snapshots don't
> replace full backups, that being the reason I don't use them here,
> since if the filesystem goes bad, it'll very likely take all the
> snapshots with it.

It is very true that snapshots do not replace full backups (in case of
software or hardware failures). However, they are a very suited
strategy to recover from unintentional deletions (most likely human,
but could also be software failures)

Best,

Lukas

-- 
+49 174 940 74 71
+64 21 150 86 86
GPG: http://lukas-pirl.de/media/attachments/lukas_pirl.pub

      parent reply	other threads:[~2015-11-08  2:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26  6:19 corrupted RAID1: unsuccessful recovery / help needed Lukas Pirl
2015-10-26  8:31 ` Duncan
2015-10-29 21:43   ` Lukas Pirl
2015-10-30  9:40     ` Duncan
2015-10-30 10:58     ` Duncan
2015-10-30 11:25       ` Hugo Mills
2015-10-30 15:03       ` Austin S Hemmelgarn
2015-11-08  2:59       ` Lukas Pirl [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=563EBA79.6040808@lukas-pirl.de \
    --to=btrfs@lukas-pirl.de \
    --cc=1i5t5.duncan@cox.net \
    --cc=ahferroin7@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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.