All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Burrett <nick@dsvr.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.20 /proc/partitions corruption with many partitions
Date: Tue, 03 Jun 2003 16:47:40 +0100	[thread overview]
Message-ID: <3EDCC31C.4080207@dsvr.net> (raw)

Hi,

I'm finding it difficult to create more than, say 80, logical partitions 
on a server.  The symptoms are that lvcreate keeps segfaulting.  The 
reason is that /proc/partitions contains invalid data.

I initially wondered whether it might be the device naming convention 
since when we go above 26 logical paritions we start writing out lvm{, 
lvm}, lvm[ etc. so I added the following patch to write out the devices 
as digits but this didn't have any effect.

--- fs/partitions/check.c 2002-11-28 23:53:15.000000000 +0000
+++ fs/partitions/check.c  2003-06-03 14:43:19.000000000 +0100
@@ -148,6 +148,7 @@ char *disk_name (struct gendisk *hd, int
                         maj = "hd";
                         break;
                 case MD_MAJOR:
+               case LVM_BLK_MAJOR:
                         sprintf(buf, "%s%d", maj, unit);
                         return buf;
         }


This is quite easy to replicate, just create many logical volumes until 
lvcreate fails e.g.

$ lvcreate -L 10M -n foo01 vol01
etc.

The attached file is simply the output of:

$ cat /proc/partitions >/root/foo.txt

Any thoughts ?


Regards,


Nick.


             reply	other threads:[~2003-06-03 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 15:47 Nick Burrett [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-03 16:00 2.4.20 /proc/partitions corruption with many partitions Nick Burrett

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=3EDCC31C.4080207@dsvr.net \
    --to=nick@dsvr.net \
    --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.