All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Chant <pete@petezilla.co.uk>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Mount issue, mount /dev/sdc2: can't read superblock
Date: Mon, 24 Dec 2018 11:36:14 +0000	[thread overview]
Message-ID: <0847f627-d918-3b63-2074-5a8313b163ab@petezilla.co.uk> (raw)
In-Reply-To: <2dfe1853-07bc-2db4-9797-5409ff74114d@gmx.com>

On 12/24/18 2:00 AM, Qu Wenruo wrote:

> I'd recommend to use "btrfs check -r 1113911951360" to verify if it's
> only superblock generation corrupted.

(cancelled  "btrfs-image -ss -c9 -t4 -w /dev/sdd2
/mnt/backup/btrfs_issue_dec_2018/btrfs_root_image_error_with_w_20181224.img"

as it said it was generating garbage).

OK, running the command:

bash-4.3# btrfs check -r 1113911951360 /dev/sdd2
Opening filesystem to check...
parent transid verify failed on 1113911951360 wanted 7937947 found 7937937
parent transid verify failed on 1113911951360 wanted 7937947 found 7937937
Ignoring transid failure
parent transid verify failed on 1113906003968 wanted 7937933 found 7937942
parent transid verify failed on 1113906003968 wanted 7937933 found 7937942
Ignoring transid failure
ERROR: cannot open file system
bash-4.3#


Not a dev so don't know what that means, but I'm assuming it is not good.


Pete





  reply	other threads:[~2018-12-24 11:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 21:21 Mount issue, mount /dev/sdc2: can't read superblock Peter Chant
2018-12-21 22:25 ` Chris Murphy
2018-12-22 12:34   ` Peter Chant
2018-12-24  0:58     ` Chris Murphy
2018-12-24  2:00       ` Qu Wenruo
2018-12-24 11:36         ` Peter Chant [this message]
2018-12-24 11:31       ` Peter Chant
2018-12-24 12:02         ` Qu Wenruo
2018-12-24 12:48           ` Tomáš Metelka
2018-12-24 13:02             ` Qu Wenruo
2018-12-24 13:52               ` Tomáš Metelka
2018-12-24 14:19                 ` Qu Wenruo
2018-12-30  0:48                   ` Broken chunk tree - Was: " Tomáš Metelka
2018-12-30  3:59                     ` Duncan
2018-12-30  4:38                     ` Qu Wenruo
2018-12-24 23:20         ` Chris Murphy

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=0847f627-d918-3b63-2074-5a8313b163ab@petezilla.co.uk \
    --to=pete@petezilla.co.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.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 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.