All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 42939] New: hv_storvsc - write cache enabled by default and cannot be disabled
Date: Thu, 15 Mar 2012 21:56:00 GMT	[thread overview]
Message-ID: <bug-42939-11613@https.bugzilla.kernel.org/> (raw)

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

           Summary: hv_storvsc - write cache enabled by default and cannot
                    be disabled
           Product: SCSI Drivers
           Version: 2.5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
        ReportedBy: bugzilla-kernel-org-sux2k0@mstier.de
        Regression: No


dmesg output:

[    8.080401] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
supports DPO and FUA

Question: how safe is my (database) data in the case of a host machine crash or
a VM crash?

There is no battery-backed writecache installed in the host, just some cheap
and slow SATA disks.

Another curiosity occurs when running the fio iometer benchmark on the same
machine: it gives me 5.000 to 6.000 I/O random access operations per second
when using the para-virt hv_storvsc driver, but only the expected 200 I/O ops
when using ata_piix via emulation.The kernel in question is version 3.2.11.

There doesn't seem to be any way to disable the para-virt device's write-cache.

Kernel version is mainline 3.2.11.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2012-03-15 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 21:56 bugzilla-daemon [this message]
2012-03-15 21:57 ` [Bug 42939] hv_storvsc - write cache enabled by default and cannot be disabled bugzilla-daemon
2012-03-19 19:33 ` bugzilla-daemon
2012-03-19 19:36 ` bugzilla-daemon

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-42939-11613@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 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.