From: Douglas Gilbert <dougg@torque.net>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFT] #2 Support for ~2144 SCSI discs, scsi_debug
Date: Sun, 12 Aug 2001 18:06:11 -0400 [thread overview]
Message-ID: <3B76FDD3.5BC5B173@torque.net> (raw)
In-Reply-To: <200108020642.f726g0L15715@mobilix.ras.ucalgary.ca> <3B735FCF.E197DD5B@torque.net> <200108100431.f7A4VkG01068@mobilix.ras.ucalgary.ca> <3B73D9F0.8BE1B0D1@torque.net> <200108102030.f7AKUfa05113@mobilix.ras.ucalgary.ca>
Richard Gooch wrote:
>
> Douglas Gilbert writes:
> > Richard Gooch wrote:
> > >
> > > Douglas Gilbert writes:
> >
> > > > $ ls -l /devfs/scsi/host46/bus0/target0/lun0/*
> > > > brw------- 1 root root 114, 16 Dec 31 1969
> > > > /devfs/scsi/host46/bus0/target0/lun0/disc
> > > > brw------- 1 root root 114, 17 Dec 31 1969
> > > > /devfs/scsi/host46/bus0/target0/lun0/part1
> > > > brw------- 1 root root 114, 18 Dec 31 1969
> > > > /devfs/scsi/host46/bus0/target0/lun0/part2
> > > > brw------- 1 root root 114, 19 Dec 31 1969
> > > > /devfs/scsi/host46/bus0/target0/lun0/part3
> > > >
> > > > Note the large major device number that devfs is pulling
> > > > from the unused pool. Devfs makes some noise when
> > > > 'rmmod scsi_debug' is executed but otherwise things looked
> > > > ok.
> > >
> > > What was the message?
> >
> > After several seconds of silence, lots of these appeared:
> > devfs_dealloc_unique_number(): number 128 was already free
> > devfs_dealloc_unique_number(): number 128 was already free
>
> I'm not able to debug this for the time being. Could you poke around
> and figure out what's happening? The first thing to check for is to
> see whether block major 128 was even allocated in the first
> place. Check /proc/devices to see (make sure you don't pass devfs=only
> at the boot line).
Richard,
/proc/devices shows the highest major number being used
by sd is 114. So block major 128 is not involved, the
error message says: "number 128".
> Next step is to hack in drivers/scsi/sd.c:sd_alloc_majors() and
> sd_dealloc_majors() and add printk() calls. Is it possible
> sd_dealloc_majors() is being called more than once?
The failure occurs when 'rmmod scsi_debug' is executed.
The sd_dealloc_majors() function is not called during that
period.
> Is 128 the only major number that it complains about? Any other
> bitching and moaning?
No just that message 166 times. I have 296 scsi devices in my
test (2 of which are real) and 2+128+166=296 . My guess is the
failure occurs near devfs_register_partitions() in
fs/partitions/check.c . Probably best if you load up scsi_debug
and look at it yourself, I'm moving onto lk 2.4.8
Doug Gilbert
next prev parent reply other threads:[~2001-08-12 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 6:42 [RFT] #2 Support for ~2144 SCSI discs Richard Gooch
2001-08-02 7:51 ` Andreas Dilger
2001-08-02 14:37 ` Richard Gooch
2001-08-10 4:15 ` [RFT] #2 Support for ~2144 SCSI discs, scsi_debug Douglas Gilbert
2001-08-10 4:31 ` Richard Gooch
2001-08-10 12:56 ` Douglas Gilbert
2001-08-10 20:30 ` Richard Gooch
2001-08-12 22:06 ` Douglas Gilbert [this message]
2001-08-13 16:23 ` Richard Gooch
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=3B76FDD3.5BC5B173@torque.net \
--to=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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.