From: James Bottomley <James.Bottomley@suse.de>
To: "Lars Täuber" <taeuber@bbaw.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: entries in sysfs regarding enclosures seem not being updated after hot plugging
Date: Fri, 22 Jan 2010 10:28:00 -0500 [thread overview]
Message-ID: <1264174080.5704.107.camel@mulgrave.site> (raw)
In-Reply-To: <20100120095733.f65474fa.taeuber@bbaw.de>
On Wed, 2010-01-20 at 09:57 +0100, Lars Täuber wrote:
> I might be wrong on this mailing list. Is there a special sysfs ML?
No, this is the right list.
> Please point me out a place to look next with my problem.
>
> I should have mentioned the kernel version and enclosure type:
> # uname -a
> Linux speicher48 2.6.31-17-server #54-Ubuntu SMP Thu Dec 10 18:06:56 UTC 2009 x86_64 GNU/Linux
> # cat /sys/class/enclosure/10\:0\:24\:0/device/vendor
> CHENBRO
> # cat /sys/class/enclosure/10\:0\:24\:0/device/model
> SASX36 B0
So the bug reports sound like something is going wrong in the device
unbinding ... I don't see what from the code, so I need to play with an
actual enclosure. Unfortunately, that can only be done when physically
present (unlike most of the SCSI development which I can do remotely),
so it has to wait until I get back home.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-22 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 10:46 scsi device is not available in enclosure any more after hot plugging Lars Täuber
2010-01-20 8:57 ` entries in sysfs regarding enclosures seem not being updated " Lars Täuber
2010-01-22 15:28 ` James Bottomley [this message]
2010-01-22 15:48 ` Lars Täuber
2010-02-19 8:08 ` Lars Täuber
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=1264174080.5704.107.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=taeuber@bbaw.de \
/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