From: "Lars Täuber" <taeuber@bbaw.de>
To: linux-scsi@vger.kernel.org
Subject: entries in sysfs regarding enclosures seem not being updated after hot plugging
Date: Wed, 20 Jan 2010 09:57:33 +0100 [thread overview]
Message-ID: <20100120095733.f65474fa.taeuber@bbaw.de> (raw)
In-Reply-To: <20100118114624.fea646be.taeuber@bbaw.de>
Hallo!
I might be wrong on this mailing list. Is there a special sysfs ML?
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
Regards
Lars
next prev parent reply other threads:[~2010-01-20 8:57 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 ` Lars Täuber [this message]
2010-01-22 15:28 ` entries in sysfs regarding enclosures seem not being updated " James Bottomley
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=20100120095733.f65474fa.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--cc=linux-scsi@vger.kernel.org \
/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