From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] /proc/partition problem
Date: Fri Aug 16 05:18:01 2002 [thread overview]
Message-ID: <20020816120315.B12990@sistina.com> (raw)
In-Reply-To: <20020815084944kaoru@rifu.bsd.tnes.nec.co.jp>; from kaoru@bsd.tnes.nec.co.jp on Thu, Aug 15, 2002 at 08:49:44AM +0900
Well, we had support for correct logical volume names ages ago already.
Hasn't been accepted by kernel folks :(
We need to live with 'nasty' names in /proc/partitions, sorry.
On Thu, Aug 15, 2002 at 08:49:44AM +0900, kaoru@bsd.tnes.nec.co.jp wrote:
> Hi,
>
> I reffered to /proc/partitions, a strange character code went
> into a name sequence when I created 26 or more volume of LV(s)
> on 2.4.19 with LVM-1.0.5.
>
> $ cat /proc/partitions
> major minor #blocks name
>
> 58 0 3145728 lvma
> 58 1 3145728 lvmb
> 58 2 512000 lvmc
> 58 3 204800 lvmd
> .........
> 58 24 53248 lvmy
> 58 25 53248 lvmz
> 58 26 53248 lvm{
> 58 27 53248 lvm|
> 58 28 53248 lvm}
> 58 29 53248 lvm~
> 58 30 53248 lvm
> 58 31 53248 lvm
> 58 32 53248 lvm
> 58 33 53248 lvm
> 58 34 53248 lvm
>
> I think that this problem is depended on illegal codes of
> a disk_name function(fs/partitions/check.c).
>
> According to fs/partitions/check.c:
>
> char *disk_name (struct gendisk *hd, int minor, char *buf)
> {
> .................
>
> if (part)
> sprintf(buf, "%s%c%d", maj, unit+'a', part);
> else
> sprintf(buf, "%s%c", maj, unit+'a');
> return buf;
>
> }
>
> I think it is better that the LVM staff discuss the fault of
> this code with Linux Kernel code maintainer.
>
> --------
> Kaoru
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-08-16 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 18:50 [linux-lvm] /proc/partition problem kaoru
2002-08-16 5:18 ` Heinz J . Mauelshagen [this message]
2002-08-16 5:59 ` Luca Berra
2002-08-16 7:31 ` Joe Thornber
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=20020816120315.B12990@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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