All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 15 Jul 2014 19:51:43 +1000	[thread overview]
Message-ID: <1462970.GnvBtDSB5Z@xev> (raw)
In-Reply-To: <CANcfdL0E+gFkVQWkzy+MJ5PZhB2y51_k3OQF+Ygekhbw=_ZrKg@mail.gmail.com>

On Tue, 15 Jul 2014 11:42:05 constantine wrote:
> Thank you very much for your advice. It worked!

Great!

> I verified that the superblocks 1 and 2 had similar information with
> btrfs-show-super -i 1 /dev/sdc1 (and -i 2) and then with crossed
> fingers:
> btrfs-select-super  -s 2 /dev/sdc1
> which restored my btrfs filesystem.
> 
> Then I runned scrub. For future reference, scrub was "stuck":
> "
> # btrfs scrub status partition/
> scrub status for c1eb1aaf-665a-4337-9d04-3c3921aa67e0
> scrub started at Thu Jul 10 21:30:41 2014, running for 2743 seconds
>    total bytes scrubbed: 193.47GiB with 0 errors
> "
> and could not cancel it:
> "
> btrfs scrub cancel partition/
> ERROR: scrub cancel failed on Downloads/: not running
> "
> After deleting
> /var/lib/btrfs/scrub.status.c1eb1aaf-665a-4337-9d04-3c3921aa67e0 it was
> completed successfully.

That's a known bug.

Now I hope you have made a good backup, the next problem you encounter may not 
be as easy to solve.

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/


      reply	other threads:[~2014-07-15  9:51 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
2014-07-15  9:42       ` constantine
2014-07-15  9:51         ` Russell Coker [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=1462970.GnvBtDSB5Z@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 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.