From: Coly Li <colyli@suse.de>
To: "Jens-U. Mozdzen" <jmozdzen@nde.ag>
Cc: linux-bcache@vger.kernel.org
Subject: Re: undo make-bcache (was: Re: Can't mount an encrypted backing device)
Date: Mon, 13 Jan 2020 22:18:14 +0800 [thread overview]
Message-ID: <0c6c3fea-5580-3a71-264c-b383b5b4fe66@suse.de> (raw)
In-Reply-To: <20200113124415.Horde.G9hpYwu_fqvg2w0msexL3ri@webmail.nde.ag>
On 2020/1/13 8:44 下午, Jens-U. Mozdzen wrote:
> Hi Coly,
>
> jumping in here, because I was looking for a way to revert from bcache
> to plain device:
>
> Zitat von Coly Li <colyli@suse.de>:
>> The super block location of the backing disk is occupied by bcache. You
>> cannot mount the file system directly from the backing disk which is
>> formated as bcache backing device [...] (bcache offset all I/Os on
>> bcache device 4KB behind the requesting
>> LBA on backing disk).
>
> Assuming that no caching device is associated with a backing device (so
> the backing device is "clean" as in "containing all data blocks with the
> current content"), could one convert the content of a backing device to
> a "non-bcached device" by removing the first 4096 octets of the backing
> device content?
>
> Something like "dd if=backingdev of=newdev skip_bytes=4096 ..."?
Hi Jens-U,
you may try dmsetup to setup a linear device mapper target, and the map
table just skipping the first 4KB (bcache superblock area). If you are
lucky, I mean the real file system is not corrupted, the created device
mapper target can be mounted directly.
--
Coly Li
next prev parent reply other threads:[~2020-01-13 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+Z73LFJLiP7Z2_cDUsO4Om_8pdD6w1jTSGQB0jY5sL-+nw1Wg@mail.gmail.com>
[not found] ` <CA+Z73LGvXa_V8t=KYPkrmeJ-xmEXmz1uAnaT=Yj5AReZgLeqhg@mail.gmail.com>
[not found] ` <alpine.LRH.2.11.2001062258320.2074@mx.ewheeler.net>
2020-01-11 13:42 ` Can't mount an encrypted backing device Clodoaldo Neto
2020-01-16 22:55 ` Eric Wheeler
2020-01-18 10:44 ` Clodoaldo Neto
[not found] ` <65c05b80-679b-2ccb-1bd1-a9a6887c9c51@suse.de>
2020-01-13 12:44 ` undo make-bcache (was: Re: Can't mount an encrypted backing device) Jens-U. Mozdzen
2020-01-13 14:18 ` Coly Li [this message]
[not found] ` <CA+Z73LGG1pBtT=0WN5vEyqEvzxEnqMRZ26S_2x4Gd5JPSmuXmQ@mail.gmail.com>
[not found] ` <CA+Z73LFNxP8kDMSq74DBKDbCXpbtMA9svpc1KddkUmrk-cfnOA@mail.gmail.com>
[not found] ` <CA+Z73LGXJOwYEb+GmPuuDi3TcJbGG=NLv-5vCRcEvB+kgr4a+A@mail.gmail.com>
2020-01-16 21:56 ` Clodoaldo Neto
2020-01-16 23:00 ` Eric Wheeler
2020-01-18 11:44 ` Clodoaldo Neto
2020-01-17 0:58 ` Coly Li
2020-01-18 10:54 ` Clodoaldo Neto
2020-01-18 12:22 ` Clodoaldo Neto
2020-01-18 12:34 ` Coly Li
2020-01-18 13:43 ` Clodoaldo Neto
2020-01-18 14:16 ` Coly Li
2020-01-18 14:31 ` Coly Li
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=0c6c3fea-5580-3a71-264c-b383b5b4fe66@suse.de \
--to=colyli@suse.de \
--cc=jmozdzen@nde.ag \
--cc=linux-bcache@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