From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: block backend issues
Date: Thu, 14 Jun 2012 14:27:12 +0200 [thread overview]
Message-ID: <4FD9D8A0.1060504@invisiblethingslab.com> (raw)
In-Reply-To: <4FD1F9E8.20508@invisiblethingslab.com>
[-- Attachment #1.1: Type: text/plain, Size: 1966 bytes --]
On 08.06.2012 15:11, Marek Marczykowski wrote:
> Hey,
>
> I've faced strange problem with block devices. When trying to read some file
> (from read-only ext3), everything looks good, except that file content is
> corrupted! But this can be coincidence (that "failed" reads doesn't hit
> filesystem metadata).
> fsck in dom0 on filesystem image returns no errors.
> fsck (with -nf flags) in domU on the device causes the kernel to output
> "blkfront: flush disk cache: empty write xvdd op failed", "blkfront: xvdd:
> barrier or flush: disable". And returns no filesystem errors. From that point,
> file reads return correct file content. For most cases dropping block cache
> (echo 3 > /proc/sys/vm/drop_caches) or remounting device also "fixes" the problem.
>
> On RW device (with different size, filesystem and content), domU kernel
> complains about EXT4 errors.
> Doesn't observed such strange issues on device-mapper backed devices.
>
> On 3.2.7 it worked, problem observed on 3.3.5 and 3.4 in dom0, regardless of
> domU kernel (tried 3.2.7, 3.3.5, 3.4.0).
>
> I've suspected feature-flush-cache/feature-barrier, but when disabled its
> advertise in blkback code, problem still occurs.
>
> Some details:
> dom0: 3.4.0-1.pvops.qubes.x86_64 (vanilla 3.4 + Konrad's patches for ACPI S3)
> domU: 3.3.5-1.pvops.qubes.x86_64 (vanilla 3.3.5 + Konrad's patches for ACPI S3)
(...)
Still the case on 3.4.1 with applied patches from Konrad's for-jens-3.5 branch.
I've compared file contents and it differs in (multiply of) 1024 bytes - the
same as filesystem block size. And only if block wasn't in pagecache in dom0.
When I flush VM pagecache (echo 1 > /proc/.../drop_caches) after trying to
read some files (actually md5sum -c), but not dom0 pagecache - problem
vanished. But if I clean also dom0 pagecache - problem returns.
Any clues welcomed...
--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-14 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 13:11 block backend issues Marek Marczykowski
2012-06-14 12:27 ` Marek Marczykowski [this message]
2012-06-15 11:14 ` Marek Marczykowski
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=4FD9D8A0.1060504@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=xen-devel@lists.xen.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.