All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ryan C. Underwood" <nemesis-lists@icequake.net>
To: Mitch Harder <mitch.harder@sabayonlinux.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Several unhappy btrfs's after RAID meltdown
Date: Tue, 7 Feb 2012 09:42:25 -0600	[thread overview]
Message-ID: <20120207154225.GD5639@localhost.localdomain> (raw)
In-Reply-To: <CAKcLGm9mLhwc1ZFp=ingR814X77QetX3LOkSqxdbussjj2gykQ@mail.gmail.com>


On Tue, Feb 07, 2012 at 08:36:15AM -0600, Mitch Harder wrote:
> 
> Since you're getting "failed to read /dev/sr0" messages, that might be
> an indication there are some newer btrfs-progs tools available.
> 
> You might want to try the building btrfs-progs from the git repository:
> http://git.kernel.org/?p=linux/kernel/git/mason/btrfs-progs.git;a=summary

I did so, here's the new output (not much changed)
# /usr/local/btrfs-progs/bin/btrfs-show
**
** WARNING: this program is considered deprecated
** Please consider to switch to the btrfs utility
**
failed to read /dev/sr0: No medium found
Label: vicep-library  uuid: 89b14d35-b31a-4fbe-a2d9-cb83cbcd3851
        Total devices 1 FS bytes used 254.35GB
        devid    1 size 1.00TB used 299.04GB path /dev/dm-32

Btrfs Btrfs v0.19

# /usr/local/btrfs-progs/bin/btrfs device scan
Scanning for Btrfs filesystems
failed to read /dev/sr0

> 
> There are some recovery tools there that may extract your data (look
> at the "recover" program).

I found a 'restore' program, are you referring to the mount option '-o
recovery'?

-- 
Ryan C. Underwood, <nemesis@icequake.net>

  reply	other threads:[~2012-02-07 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-05 18:41 Several unhappy btrfs's after RAID meltdown Ryan C. Underwood
2012-02-07  3:39 ` Ryan C. Underwood
2012-02-07  4:17   ` Liu Bo
2012-02-07 15:03     ` Ryan C. Underwood
2012-02-07  9:53   ` Duncan
2012-02-07 14:04     ` Ryan C. Underwood
2012-02-07 14:36       ` Mitch Harder
2012-02-07 15:42         ` Ryan C. Underwood [this message]
2012-02-07 17:46           ` Ryan C. Underwood
2012-02-07 17:49             ` Ryan C. Underwood
2012-02-12 16:31               ` Ryan C. Underwood
2012-02-13 13:48                 ` David Sterba
2012-06-01 14:38                 ` Ryan C. Underwood
2012-11-15 16:00                   ` Ryan C. Underwood
2012-11-16  8:39                     ` Michael Kjörling
2012-02-08  6:32     ` Chris Samuel

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=20120207154225.GD5639@localhost.localdomain \
    --to=nemesis-lists@icequake.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mitch.harder@sabayonlinux.org \
    --cc=nemesis@icequake.net \
    /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.