From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 42939] hv_storvsc - write cache enabled by default and cannot be disabled
Date: Mon, 19 Mar 2012 19:33:30 GMT [thread overview]
Message-ID: <201203191933.q2JJXU7i027495@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42939-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42939
--- Comment #1 from Mark <bugzilla-kernel-org-sux2k0@mstier.de> 2012-03-19 19:33:29 ---
Additional information:
trying to disable the writecache leads to the partition on the SCSI device
getting remounted read-only due to device errors.
Additional information (2):
I get 5.000 to 6.000 random reads per second even when manually creating the
fiometer file using random data from /dev/urandom (ie. fio doesn't access
zeroes in that case).
Additional information (3):
The host doesn't seem to cache anything: "dd iflag=direct if=/dev/sda bs=1M
of=/dev/null count=10" always and repeatedly gives me around 30-60 MB/s.
Additional information (4):
I did a simple MySQL InnoDB ACID transaction test where subsequent transactions
are done via a remote mysql client as fast as possible. I crashed the host
hardware and checked if all transactions reported as completed had been
committed to disk: no obvious problems there -- seemingly the reported
writecache has no writecache-effects at all...??
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-03-19 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 21:56 [Bug 42939] New: hv_storvsc - write cache enabled by default and cannot be disabled bugzilla-daemon
2012-03-15 21:57 ` [Bug 42939] " bugzilla-daemon
2012-03-19 19:33 ` bugzilla-daemon [this message]
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=201203191933.q2JJXU7i027495@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.