From: Anders Gustafsson <andersg@0x63.nu>
To: Andries.Brouwer@cwi.nl
Cc: davej@suse.de, andersg@0x63.nu, linux-kernel@vger.kernel.org,
whitney@adsl-209-76-109-63.dsl.snfc21.pacbell.net
Subject: Re: /proc/partitions broken in 2.5.23
Date: Fri, 21 Jun 2002 01:42:52 +0200 [thread overview]
Message-ID: <20020620234252.GA3166@h55p111.delphi.afb.lu.se> (raw)
In-Reply-To: <UTC200206202321.g5KNLeT22807.aeb@smtp.cwi.nl>
On Fri, Jun 21, 2002 at 01:21:40AM +0200, Andries.Brouwer@cwi.nl wrote:
> > I got a bug report about an issue with LVM in 2.5.22-dj1, which turns
> > out to be caused by broken /proc/partitions in mainline.
> >
> > (davej@mesh:davej)$ cat /proc/partitions
> > major minor #blocks name
> >
> > 8 0 0 sda
> > 22 0 1515870810 hdc
> >
> > Note the huge numbers in hex are 0x5a5a5a5a, so something
> > seems to be getting poisoned somewhere.
>
> Is this LVM?
>
> I don't see how LVM could produce such values.
> (And in fact LVM does not even compile, so only a patched LVM
> could produce anything at all.)
Me neither. And as a datapoint: with my lvm-cleanup-patch I get
correct size-values for all my partitions (but, yes, all 0-sized LVs
shows). But there is a problem with my /proc/partitions, i starts with
2 pages of garbage (8k). Is this some kind of overflow problem as lvm
creates 256 entries?
--
//anders/g
next prev parent reply other threads:[~2002-06-20 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 23:21 Andries.Brouwer
2002-06-20 23:34 ` Dave Jones
2002-06-20 23:42 ` Anders Gustafsson [this message]
[not found] <641481775@toto.iv>
2002-06-26 3:22 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 9:02 Dave Jones
2002-06-19 11:32 ` Andries Brouwer
2002-06-19 11:44 ` Dave Jones
2002-06-19 12:51 ` Andries Brouwer
2002-06-19 13:16 ` Dave Jones
2002-06-19 17:18 ` Wayne Whitney
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=20020620234252.GA3166@h55p111.delphi.afb.lu.se \
--to=andersg@0x63.nu \
--cc=Andries.Brouwer@cwi.nl \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@adsl-209-76-109-63.dsl.snfc21.pacbell.net \
/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®