From: Cliff White <cliffw@osdl.org>
To: James Stevenson <james@stev.org>
Cc: Per Andreas Buer <perbu@linpro.no>,
linux-kernel@vger.kernel.org, cliffw@osdl.org
Subject: Re: iostats broken for devices with major number > DK_MAX_DISK (16)
Date: Tue, 12 Nov 2002 15:25:43 -0800 [thread overview]
Message-ID: <200211122325.gACNPhr08344@mail.osdl.org> (raw)
In-Reply-To: Message from James Stevenson <james@stev.org> of "12 Nov 2002 23:01:03 GMT." <1037142064.1570.0.camel@god.stev.org>
> On Tue, 2002-11-12 at 20:35, Per Andreas Buer wrote:
> > Hi,
> >
> > sorry for the intrusion. I noticed iostats didn't display statistics for
> > devices on Mylex RAID constrollers. Det statistics are completely
> > missing in /proc/stat. The reason seems to be an assumption that disks
> > have major numbers which are below 16
> > (http://lxr.linux.no/source/include/linux/kernel_stat.h#L15) which is
> > used by http://lxr.linux.no/source/fs/proc/proc_misc.c#L344.
> >
> > Devices on Mylex-controllers have major number 48. Would it break
> > anything if DK_MAX_MAJOR if set higher (e.g. 64)?
> >
> > AFAIK this goes for both 2.4 and the 2.5 series.
>
> i have been runing with 2.4.x kernel with this number
> set higher i have still yet to see any problem with it
> other than using more memory.
>
We've had the same problem, and we've been running with DK_MAX_MAJOR == 64,
using megaraid and acceleraid 2000 controllers.
Haven't seen any problems
cliffw
OSDL
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-11-12 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 20:35 Per Andreas Buer
2002-11-12 23:01 ` James Stevenson
2002-11-12 23:25 ` Cliff White [this message]
2002-11-12 23:40 ` James Stevenson
2002-11-12 23:41 ` Rick Lindsley
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=200211122325.gACNPhr08344@mail.osdl.org \
--to=cliffw@osdl.org \
--cc=james@stev.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perbu@linpro.no \
/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®