From: Michael Tokarev <mjt@tls.msk.ru>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Random scsi disk disappearing
Date: Thu, 17 Aug 2006 15:43:55 +0400 [thread overview]
Message-ID: <44E4567B.4080104@tls.msk.ru> (raw)
In-Reply-To: <20060817113537.GK4340@parisc-linux.org>
Matthew Wilcox wrote:
> On Thu, Aug 17, 2006 at 02:55:58PM +0400, Michael Tokarev wrote:
[sporadic disk disappearing, no logging]
>
> I'd recommend turning on scsi logging; it might give you a clue about
> which bit of scanning is failing to work properly.
>
> Try booting with scsi_mod.scsi_logging_level = 448 (I think I have that
> number right; 7 shifted left by 6) and then you can compare failing and
> non-failing runs and see if there's any difference.
It should be the same as
echo $((7<<6)) > /sys/module/scsi_mod/parameters/scsi_logging_level
(which indeed is 448) at runtime, right? (And yes, CONFIG_SCSI_LOGGING
is set to y).
Heh oh those magic numbers!.. ;)
Ok, I've turned on the logging on a bunch of machines (using the sysfs
method), let's see what will happen next. Thank you!
By the way, should kernel pefrorm at least *some* "minimal" logging of
such a serious events by default? Well ok, ok, it's not known yet what
the event really is, so I'm shutting up now, at least for a while.. ;)
/mjt
next prev parent reply other threads:[~2006-08-17 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-17 10:55 Random scsi disk disappearing Michael Tokarev
2006-08-17 11:35 ` Matthew Wilcox
2006-08-17 11:43 ` Michael Tokarev [this message]
2006-08-17 11:53 ` Matthew Wilcox
2006-08-17 13:41 ` Jan Engelhardt
2006-08-17 16:48 ` Andreas Herrmann
2006-08-17 22:33 ` Stefan Richter
2006-08-30 19:40 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 9:11 Andreas Herrmann
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=44E4567B.4080104@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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