From: "Yajith Ajantha Dayarathna | යජිත් අජන්ත දයාරත්න" <yajith@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvcreate problem
Date: Wed, 13 Feb 2008 15:43:41 +0530 [thread overview]
Message-ID: <b646832c0802130213l3b7eaaf5t1fa0246553904b07@mail.gmail.com> (raw)
In-Reply-To: <47B2BF41.8070701@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
On Feb 13, 2008 3:28 PM, Bryn M. Reeves <breeves@redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yajith Ajantha Dayarathna | ????? ????? ??????? wrote:
> > even though the fdisk output contains "/dev/cciss/c0d0p16" there is no
> > such device created under /dev/cciss/.
> > Is it because of the above mentioned limitation ?
>
> That's correct - under Linux, IDE hard disks (/dev/hd*) can have up to
> 63 partitions but SCSI and RAID controllers like the CCISS are limited
> to 15 partitions (16 if you count the whole-device) due to the way minor
> numbers are allocated to /dev/sd* nodes.
>
> You could cheat and map the additional partitions using kpartx - run
> "kpartx -a /dev/cciss/c0d0" and this should create a device-mapper
> device for each partition under /dev/mapper/c0d0p*. You can remove them
> again with "kpartx -d /dev/cciss/c0d0".
>
> That said, it might be better to reconsider your partitioning scheme and
> see if you really need that number of partition table entries.
>
> Regards,
> Bryn.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFHsr9B6YSQoMYUY94RAmWfAJ4uXdCCtqX8nKiER8yXqNoHFHaVkQCeOOdM
> R3aCmQuHBVUxP/9bbGvrrqg=
> =EUlc
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
i will try the mapper device.
yes, the partitioning scheme is quite inflexible.
Does LVM use the same technique to get around this limitation ? I have seen
devices getting created under /dev/mapper.
Always thought its a part of LVM.
thanks a lot for all your support...
--
Yajith Ajantha
[-- Attachment #2: Type: text/html, Size: 2469 bytes --]
next prev parent reply other threads:[~2008-02-13 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 8:13 [linux-lvm] pvcreate problem Yajith Ajantha Dayarathna | යජිත් අජන්ත දයාරත්න
2008-02-13 8:37 ` Mark Huth
2008-02-13 9:04 ` Yajith Ajantha Dayarathna | යජිත් අජන්ත දයාරත්න
2008-02-13 9:06 ` Yajith Ajantha Dayarathna | යජිත් අජන්ත දයාරත්න
2008-02-13 9:58 ` Bryn M. Reeves
2008-02-13 10:13 ` Yajith Ajantha Dayarathna | යජිත් අජන්ත දයාරත්න [this message]
2008-02-13 10:35 ` Bryn M. Reeves
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 17:27 Alexander Lazarevich
2002-12-06 8:56 ` Alexander Lazarevich
2002-12-06 8:59 ` Heinz J . Mauelshagen
2002-12-06 9:26 ` Alexander Lazarevich
2002-12-09 5:13 ` Heinz J . Mauelshagen
2002-01-02 2:13 Colin Coe
2002-01-02 2:46 ` Luca Berra
2002-01-02 11:59 ` Kirby C. Bohling
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=b646832c0802130213l3b7eaaf5t1fa0246553904b07@mail.gmail.com \
--to=yajith@gmail.com \
--cc=linux-lvm@redhat.com \
/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).