Linux-BTRFS Archive on lore.kernel.org
 help / color / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: "Jiří Lisický" <jiri_lisicky@seznam.cz>,
	"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: I can't mount image
Date: Sat, 23 May 2020 17:21:33 -0600
Message-ID: <CAJCQCtQmTan=rrRJ2ALM25DnUt05Xdsuae9GR88L5mB=OR+QVA@mail.gmail.com> (raw)
In-Reply-To: <3bc39223e567b7a4eca13bc554c74ef0c36fbaf2.camel@seznam.cz>

On Sat, May 23, 2020 at 8:38 AM Jiří Lisický <jiri_lisicky@seznam.cz> wrote:
>
> [root@localhost-live tmp] # btrfs rescue super -v /dev/loop4
> All Devices:
>         Device: id = 1, name = /dev/loop4
>
> Before Recovering:
>         [All good supers]:
>                 device name = /dev/loop4
>                 superblock bytenr = 65536
>
>                 device name = /dev/loop4
>                 superblock bytenr = 67108864
>
>         [All bad supers]:
>
> All supers are valid, no need to recover

OK. So they're good.

>
>
>
> [root@localhost-live tmp]# mount -o ro,recovery /dev/loop4 ./mnt
> mount: /home/jirka/tmp/mnt: can't read superblock on /dev/loop4.


But it can't be read? This doesn't make sense. What kernel messages
are reported at the time of the mount attempt? When using a newer
kernel, the recovery command is deprecated but should still work. The
new command is 'usebackuproot'

What do you get for:

# btrfs insp dump-s -fa /dev/

-- 
Chris Murphy

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 19:51 Jiří Lisický
2020-05-18 23:45 ` Chris Murphy
2020-05-20 21:12   ` Jiří Lisický
2020-05-20 21:54     ` Chris Murphy
2020-05-23 14:38       ` Jiří Lisický
2020-05-23 23:21         ` Chris Murphy [this message]
2020-05-24 19:51           ` Jiří Lisický
2020-05-23 23:27         ` 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='CAJCQCtQmTan=rrRJ2ALM25DnUt05Xdsuae9GR88L5mB=OR+QVA@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=jiri_lisicky@seznam.cz \
    --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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org
	public-inbox-index linux-btrfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git