linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe David Manana <fdmanana@gmail.com>
To: Andreas Philipp <philipp.andreas@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Snapshot cannot be deleted
Date: Wed, 21 Jan 2015 12:26:07 +0000	[thread overview]
Message-ID: <CAL3q7H6+hdRSE_3E8NsR=NekUeLJxS6rcVBstYPriJfnfRLM-Q@mail.gmail.com> (raw)
In-Reply-To: <CAKVY-+9cjRKfXFVVEamtNVLaWE1+jc44M4kyrJOOk915v2fxtA@mail.gmail.com>

On Tue, Jan 20, 2015 at 12:28 PM, Andreas Philipp
<philipp.andreas@gmail.com> wrote:
> Hi,
>
> Due to the known (and fixed) bug in kernel 3.17.0 one of my btrfs
> volume suffers from unreadable and - even worse - uneraseable
> snapshots. Whenever such a snapshot is accessed there is "parent
> transid verify failed" in dmesg.
> Is there any way to delete these snapshots?

It can be fixed with btrfs-progs v3.17 and later (3.18.x is the latest release).
To confirm that you are affected by the 3.17 kernel issue, run btrfsck
in readonly mode first (without --repair or any other flags), which
will print one message with the following format for each corrupt
snapshot:

"root %llu has a root item with a more recent gen (%llu) compared to
the found root node (%llu)\n"

Any other error messages are likely unrelated and therefore associated
with other eventual issues.
As usual, before running btrfsck with --repair (which fixes the issue
and the snapshots will be fully repaired), create backups of your
data.

Hope it helps.

>
> Thanks,
> Andreas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Filipe David Manana,

"Reasonable men adapt themselves to the world.
 Unreasonable men adapt the world to themselves.
 That's why all progress depends on unreasonable men."

      parent reply	other threads:[~2015-01-21 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKVY-+9cjRKfXFVVEamtNVLaWE1+jc44M4kyrJOOk915v2fxtA@mail.gmail.com>
2015-01-20 17:13 ` Snapshot cannot be deleted Theodore Ts'o
2015-01-21 12:26 ` Filipe David Manana [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='CAL3q7H6+hdRSE_3E8NsR=NekUeLJxS6rcVBstYPriJfnfRLM-Q@mail.gmail.com' \
    --to=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=philipp.andreas@gmail.com \
    /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).