From: Gleb Natapov <gleb@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: the >1Tb block issue
Date: Tue, 18 May 2010 19:58:31 +0300 [thread overview]
Message-ID: <20100518165831.GC1319@redhat.com> (raw)
In-Reply-To: <4BF2C5AB.7080105@msgid.tls.msk.ru>
On Tue, May 18, 2010 at 08:51:55PM +0400, Michael Tokarev wrote:
> 18.05.2010 19:52, Michael Tokarev wrote:
> >I just re-verified it on current stable
> >qemu-kvm-0.12.4. The issue is still here,
> >trivial to trigger.
> >
> >kvm-img create test.raw 1500G
> >kvm ... \
> >-drive file=test.raw,if=virtio
> >
> >it fails right on the mkfs stage:
> >
> >mkfs.ext4 /dev/vdb
> >Writing inode tables: end_request: I/O error, dev vdb, sector 3145727872
> >Buffer I/O error on device vdb, logical block 393215984
> >lost page write due to I/O error on vdb
> >Buffer I/O error on device vdb, logical block 393215985
> >...
> >Buffer I/O error on device vdb, logical block 393215993
> >
> >After that it continues the mkfs process, but I doubt it will
> >produce a good filesystem.
>
> A few more data point, for what it's worth.
>
> I tried running it under strace, but in that case the issue does
> not occur: mkfs wents on without errors. That puzzles me: timing
> problem?
>
> It always fails at the same place: sector 3145727872. This
> is - apparently - somewhere at the end of my 1500Gb file.
>
Hmmm. 3145727872*512 = 0xffff0000
--
Gleb.
next prev parent reply other threads:[~2010-05-18 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:52 the >1Tb block issue Michael Tokarev
2010-05-18 15:59 ` Daniel P. Berrange
2010-05-18 16:51 ` Michael Tokarev
2010-05-18 16:58 ` Gleb Natapov [this message]
2010-05-18 17:29 ` Avi Kivity
2010-05-18 17:34 ` Michael Tokarev
2010-05-18 17:38 ` Avi Kivity
2010-05-18 18:03 ` Michael Tokarev
2010-05-18 18:09 ` Avi Kivity
2010-05-18 18:38 ` Michael Tokarev
2010-05-18 18:43 ` Michael Tokarev
2010-05-19 8:57 ` Christoph Hellwig
2010-05-19 9:03 ` Avi Kivity
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=20100518165831.GC1319@redhat.com \
--to=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.