public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 16490] "Assuming drive cache: write through" messages probably have wrong loglevel
Date: Wed, 04 Jun 2014 14:19:03 +0000	[thread overview]
Message-ID: <bug-16490-11613-vR11V2gL19@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-16490-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=16490

Alain Kalker <a.c.kalker@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |a.c.kalker@gmail.com

--- Comment #8 from Alain Kalker <a.c.kalker@gmail.com> ---
I submitted a patch to lower the log level to the linux-scsi mailing list.
The patch was not accepted; James Bottomley offered this very insightful
explanation why the log level should remain high (quoted here for those who are
not reading the linux-scsi mailing list):

> [...] The condition may be an error.  We have
> some USB attached storage devices with writeback caches which don't
> supply caching information.  Treating a writeback device as writethrough
> is a potential error because you may lose data as a result of it.
> 
> The error is that we've made an assumption which may damage your data.
> 
> The problem for us is that we can't tell if the assumption is going to
> be fatal or not ... the message is harmless for older USB devices.

>From doing a little research, I would suggest these steps to mitigate the risk
(correct me if I'm wrong or have omitted anything):

- Find out if the device has write cache enabled by default, by consulting its
documentation, technical specifications, or by contacting the manufacturer.
- If the device does have write cache enabled, a quirk parameter can be added
to either the kernel commandline or as a module parameter for the usb-storage
module[1]
- Verify that the device works as expected.

[1] For more information on USB storage device quirks and how to configure
them, see linux/Documentation/kernel-parameters.txt in the Linux kernel source.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2014-06-04 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16490-11613@https.bugzilla.kernel.org/>
2010-08-05 14:09 ` [Bug 16490] "Assuming drive cache: write through" messages probably have wrong loglevel bugzilla-daemon
2014-06-04 14:19 ` bugzilla-daemon [this message]

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=bug-16490-11613-vR11V2gL19@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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