From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Partitioned loop devices, support for 127 Partitions on SATA, IDE and SCSI
Date: Wed, 10 Nov 2004 11:05:46 +0500 [thread overview]
Message-ID: <cmsb12$pr1$1@sea.gmane.org> (raw)
In-Reply-To: 419199A3.3050806@gmx.net
Carl-Daniel Hailfinger wrote:
> Hi,
>
> having seen the problems people have when switching from traditional IDE
> drivers to libata if they have more than 15 partitions, I decided to do
> something against it. With this patch (and recreating /dev/loop* nodes)
> it is possible to support up to 127 partitions per loop device
> regardless what the underlying device supports. It works for me
> and has the added bonus that it will be in compatibility mode as long
> as you don't specify the max_part parameter.
>
> To make migration to the new loop version easy, the new default loop
> behaviour is exactly the same as the old one, so you should not notice
> any breakage. However, if you decide to enable partitioned loop support
> by specifying the max_part parameter, loop devices will have major
> number 240, currently reserved for local/experimental use, and loopN
> will have the minor range [N*max_part, (N+1)*max_part-1].
>
> For even easier migration, the partition table will NOT be read by
> default on losetup so you even can use unpartitioned loop devices when
> being no longer in compat mode. If you want to activate partitions for
> /dev/loopN, just issue "blockdev --rereadpt /dev/loopN" and the
> partitions will magically appear in /sys/block/loopN/.
Why not just use EVMS? Partition code is supposed to be moved to userspace
anyway.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2004-11-10 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 4:31 [PATCH] Partitioned loop devices, support for 127 Partitions on SATA, IDE and SCSI Carl-Daniel Hailfinger
2004-11-10 6:05 ` Alexander E. Patrakov [this message]
2004-11-11 4:54 ` Carl-Daniel Hailfinger
2004-11-11 13:55 ` Alexander E. Patrakov
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='cmsb12$pr1$1@sea.gmane.org' \
--to=patrakov@ums.usu.ru \
--cc=linux-kernel@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.