From: Russell Coker <russell@coker.com.au>
To: constantine <costas.magnuse@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs and LBA errors
Date: Sat, 12 Jul 2014 11:23:38 +1000 [thread overview]
Message-ID: <3431118.WpiWX9X6ip@xev> (raw)
In-Reply-To: <CANcfdL1Ldf0-Bbe16bRyUtA+cpupTzqYLdzmHrsOJacE5c92Lw@mail.gmail.com>
On Fri, 11 Jul 2014 21:29:07 constantine wrote:
> Thank you very much for your response:
>
> # file -s /dev/sda1 /dev/sdc1
> /dev/sda1: BTRFS Filesystem label "partition", sectorsize 4096,
> nodesize 4096, leafsize 4096,
> UUID=c1eb1aaf-665a-4337-9d04-3c3921aa67e0, 1683870334976/3010310701056
> bytes used, 2 devices
> /dev/sdc1: data
Looks like the primary superblock on /dev/sdc1 is corrupt.
http://www.funtoo.org/BTRFS_Fun#btrfs-select-super_.2F_btrfs-zero-log
The above URL documents how to use the other superblocks. It notes that you
only get one chance - if you do this wrong you will dramatically reduce the
probability of getting your data back. Do not do this on the master copy of
your data!
Buy 2 disks of equal or greater capacity, copy the block devices, and then
working with the copy. sdc needs to be replaced anyway no matter what you do
and getting a replacement for sda would be a good strategy anyway. Buy 2*4TB
disks and you can make a new RAID-1 array that has more capacity than the non-
RAID filesystem you currently have.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-07-12 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 11:42 Btrfs and LBA errors constantine
2014-07-11 12:36 ` Russell Coker
2014-07-11 19:29 ` constantine
2014-07-12 1:23 ` Russell Coker [this message]
2014-07-15 9:42 ` constantine
2014-07-15 9:51 ` Russell Coker
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=3431118.WpiWX9X6ip@xev \
--to=russell@coker.com.au \
--cc=costas.magnuse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).