All of lore.kernel.org
 help / color / mirror / Atom feed
From: David T-G <davidtg+robot@justpickone.org>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: can't loop the image files and assemble (was "Re: overlays on dd images of 4T drives")
Date: Tue, 16 Nov 2021 02:07:56 +0000	[thread overview]
Message-ID: <20211116020756.GA120503@opal1.opalstack.com> (raw)
In-Reply-To: <20211116020126.GA95566@opal1.opalstack.com>

Hi again, all --

...and then David T-G said...
% 
...
% 
% Can I create loopback devices pointing to the image files, which will
% give me raw handles, and then assemble that?
[snip]

Apparently that's a "no":

  diskfarm:/mnt/10Traid50md/tmp # losetup -r /dev/loop10 `pwd`/4Tsda1*
  diskfarm:/mnt/10Traid50md/tmp # losetup -r /dev/loop11 `pwd`/4Tsdb1*
  diskfarm:/mnt/10Traid50md/tmp # losetup -r /dev/loop12 `pwd`/4Tsdc1*

  diskfarm:/mnt/10Traid50md/tmp # losetup -a | grep 4T
  /dev/loop11: [66326]:1054 (/mnt/10Traid50md/tmp/4Tsdb1.5YD9.dd-bs=256M-conv=sparse,noerror)
  /dev/loop12: [66326]:1055 (/mnt/10Traid50md/tmp/4Tsdc1.5ZY3.dd-bs=256M-conv=sparse,noerror)
  /dev/loop10: [66326]:1028 (/mnt/10Traid50md/tmp/4Tsda1.EYNA.dd-bs=256M-conv=sparse,noerror)
  # hey ... i did those manually and in order! *sigh*

  diskfarm:/mnt/10Traid50md/tmp # mdadm --assemble /dev/md4 /dev/loop1{0,1,2}
  mdadm: /dev/loop10 is busy - skipping
  mdadm: /dev/loop11 is busy - skipping
  mdadm: /dev/loop12 is busy - skipping

Scratch that idea ...


:-D
-- 
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt


      reply	other threads:[~2021-11-16  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14  2:29 overlays on dd images of 4T drives David T-G
2021-11-14  8:47 ` Roman Mamedov
2021-11-15  2:51 ` David T-G
2021-11-15 19:32   ` Phillip Susi
2021-11-16  2:01     ` David T-G
2021-11-16  2:07       ` David T-G [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=20211116020756.GA120503@opal1.opalstack.com \
    --to=davidtg+robot@justpickone.org \
    --cc=linux-raid@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 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.