mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Corry <kevcorry@us.ibm.com>
To: "Dimitry V. Ketov" <Dimitry.Ketov@avalon.ru>,
	"Lars Marowsky-Bree" <lmb@suse.de>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Partitioned loop device..
Date: Wed, 16 Jul 2003 08:51:18 -0500	[thread overview]
Message-ID: <200307160851.18967.kevcorry@us.ibm.com> (raw)
In-Reply-To: <E1B7C89B8DCB084C809A22D7FEB90B3840AE@frodo.avalon.ru>

On Wednesday 16 July 2003 03:59, Dimitry V. Ketov wrote:
> > There is no difference. What makes /dev/loop1a worse than
> > /dev/hda1? It's just block devices, that's it.
>
> Yes, it is. But I meant its still impossible to use legacy fdisk to
> create that DM mapped partitions (or am I wrong?)

The program fdisk does not know about Device-Mapper. It only reads and writes 
DOS partition tables, and leaves it up to the kernel block-layer to provide 
the corresponding block devices. Other tools are available that use the same 
partitioning format and work with Device-Mapper.

> > I have hopes that the entire partitioning code etc will be
> > ripped out in 2.7 in favour of full userspace discovery + DM,
> > and that MD will hit the same fate...
>
> MD - did you mean metadisks (software raids?)

Yes. Software RAID devices are currently handled by the MD driver, but much of 
that functionality could be ported to Device-Mapper. RAID-linear and RAID-0 
can already be supported in DM, and the latest DM release from Sistina has a 
module to support RAID-1. So all that's left is to port the RAID-5 code to a 
DM module, and modify the user-space tools.

-- 
Kevin Corry
kevcorry@us.ibm.com
http://evms.sourceforge.net/


  reply	other threads:[~2003-07-16 13:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  8:59 Dimitry V. Ketov
2003-07-16 13:51 ` Kevin Corry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 18:32 Dimitry V. Ketov
2003-07-15 21:15 ` Lars Marowsky-Bree
2003-07-18 14:20 ` Christophe Saout
2003-07-18 19:10   ` Mr. James W. Laferriere
2003-07-18 23:57     ` Christophe Saout
2003-07-15  8:46 Dimitry V. Ketov
2003-07-15 15:01 ` Kevin Corry
2003-07-15 15:53   ` Josh Litherland
2003-07-15 16:04     ` Kevin Corry
2003-07-15 16:05     ` Herbert Pötzl
2003-07-17  2:44     ` kernel
2003-07-15  7:10 Dimitry V. Ketov

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=200307160851.18967.kevcorry@us.ibm.com \
    --to=kevcorry@us.ibm.com \
    --cc=Dimitry.Ketov@avalon.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@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

all inboxes | Powered by JetHome®