linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Linux Raid List <linux-raid@vger.kernel.org>
Cc: Neil Brown <neilb@suse.de>
Subject: Re: Can I abuse md like this?
Date: Sat, 30 Dec 2006 17:15:14 -0500	[thread overview]
Message-ID: <4596E4F2.2060201@tmr.com> (raw)
In-Reply-To: <45902232.6000706@tmr.com>

Bill Davidsen wrote:
> Neil Brown wrote:
>> On Saturday December 23, davidsen@tmr.com wrote:
>>  
>>> I hope I can use the md code to solve a problem, although in a way 
>>> probably not envisioned by the author(s).
>>>
>>> I have a disk image, a physical dump of every sector from start to 
>>> finish, including the partition table. What I hope I can do is to 
>>> create a one drive RAID-1 partitionable array, and then access it 
>>> with fdisk or similar. These partitions are not "nice" types such as 
>>> FAT, VFAT, ext2, etc, this is an odd disk, and I "saved it" by 
>>> saving everything. Now I'd like to start dismembering the 
>>> information and putting it into useful pieces. I even dare to hope 
>>> that I could get the original software running on a virtual machine 
>>> at some point.
>>>
>>> The other alternative is to loopback mount it, I'm somewhat 
>>> reluctant to do that if I can avoid it.
>>>
>>> Yes, the partition table is standard in format if not in content.
>>>     
>>
>> Maybe...
>> Is this image in a file?
>> md only works with block devices, so you would need to use the 'loop'
>> driver to create a block-device "/dev/loopX".
>>   
> I was thinking nbd, actually.
>> But as loop devices cannot be partitioned, you could then
>>   mdadm -Bf /dev/md/d9 -amdp8 -l1 -f -n1 /dev/loopX
>>   and then look at the partitions in /dev/md/d9_*
>>
>> Should work.
> Sounds worth a try. Will be a learning experience if nothing else.
>
Rather than setup nbd I did try a loop mount, and the whole process 
worked flawlessly. I was able to look at partitions, read the partition 
table, and generally do anything I could from a device. It worked so 
well I backed it up as an image, just in case I ever want to do 
something else with it.

Many thanks.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      reply	other threads:[~2006-12-30 22:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-24  3:35 Can I abuse md like this? Bill Davidsen
2006-12-24  3:44 ` Neil Brown
2006-12-25 19:10   ` Bill Davidsen
2006-12-30 22:15     ` Bill Davidsen [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=4596E4F2.2060201@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).