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 [thread overview]
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
next prev parent reply other threads:[~2020-05-23 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 19:51 I can't mount image 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
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).