From: Jens Axboe <axboe@fb.com>
To: <sedat.dilek@gmail.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Ming Lei <ming.lei@canonical.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0
Date: Sun, 22 Feb 2015 08:06:10 -0800 [thread overview]
Message-ID: <54E9FE72.2070505@fb.com> (raw)
In-Reply-To: <CA+icZUXgSabOHbay49Tnh04gq2nox852-muhTJNF3ionrER0mg@mail.gmail.com>
On 02/22/2015 06:09 AM, Sedat Dilek wrote:
> Hi,
>
> when testing Linux-next (upcoming v3.20) I fell over similiar messages
> when running fio here.
>
> This commit helped which is now upstream [1]...
>
> commit 9f9ee1f2b2f94f19437ae2def7c0d6636d7fe02e
> "block: Quiesce zeroout wrapper"
>
> --- dmesg_3.19.0-9526.2-iniza-small_before-fio-2.2.5.txt
> 2015-02-22 14:09:35.411824880 +0100
> +++ dmesg_3.19.0-9526.2-iniza-small_after-fio-2.2.5.txt 2015-02-22
> 14:10:25.327824500 +0100
> @@ -853,3 +853,25 @@
> [ 428.226000] Adding 36k swap on swapfile29. Priority:-29 extents:1
> across:36k FS
> [ 469.339645] Process 7691(waitpid02) has RLIMIT_CORE set to 1
> [ 469.339650] Aborting core
> +[ 1877.189057] fio-testcase.sh (10238): drop_caches: 3
> +[ 1882.250174] blk_update_request: I/O error, dev loop0, sector 2883712
> +[ 1882.807993] blk_update_request: I/O error, dev loop0, sector 32460632
> +[ 1884.655458] blk_update_request: I/O error, dev loop0, sector 16869712
> +[ 1884.656896] blk_update_request: I/O error, dev loop0, sector 16854368
> +[ 1884.659316] blk_update_request: I/O error, dev loop0, sector 16855008
> +[ 1884.660834] blk_update_request: I/O error, dev loop0, sector 16869792
> +[ 1884.661780] blk_update_request: I/O error, dev loop0, sector 16854848
> +[ 1884.663282] blk_update_request: I/O error, dev loop0, sector 16855432
> +[ 1884.664775] blk_update_request: I/O error, dev loop0, sector 16859808
> +[ 1884.671472] blk_update_request: I/O error, dev loop0, sector 16866400
> +[ 1892.239383] blk_update_request: 20 callbacks suppressed
> +[ 1892.239389] blk_update_request: I/O error, dev loop0, sector 7872768
> +[ 1897.221576] blk_update_request: I/O error, dev loop0, sector 23331008
> +[ 1898.299271] blk_update_request: I/O error, dev loop0, sector 25690688
> +[ 1898.444161] blk_update_request: I/O error, dev loop0, sector 25726496
> +[ 1898.445946] blk_update_request: I/O error, dev loop0, sector 25690832
> +[ 1898.448185] blk_update_request: I/O error, dev loop0, sector 25692312
> +[ 1898.449321] blk_update_request: I/O error, dev loop0, sector 25704840
> +[ 1898.450314] blk_update_request: I/O error, dev loop0, sector 25710392
> +[ 1898.451351] blk_update_request: I/O error, dev loop0, sector 25726080
> +[ 1898.452348] blk_update_request: I/O error, dev loop0, sector 25737608
>
> FYI: This is with Linux-v3.19-9526-ga135c717d5cd plus vfs.git#for-linus.
This really has nothing to do with commit 9f9ee1f2b2f, other than that
they both have some block related messages. The above is normal IO
errors on the device, we expect to see messages related to that. The
question is mostly why you are seeing those. What are you running on the
device?
And is this a regression since 3.19?
--
Jens Axboe
next prev parent reply other threads:[~2015-02-22 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 14:09 [Linux-v3.19-9526-ga135c717d5cd + vfs.git] blk_update_request: I/O error, dev loop0 Sedat Dilek
2015-02-22 14:21 ` Sedat Dilek
2015-02-22 16:06 ` Jens Axboe [this message]
2015-02-22 20:02 ` Sedat Dilek
2015-02-22 20:04 ` Jens Axboe
2015-02-22 20:12 ` Sedat Dilek
2015-02-23 3:10 ` Ming Lei
2015-02-23 4:33 ` Jens Axboe
2015-02-23 7:16 ` Sedat Dilek
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=54E9FE72.2070505@fb.com \
--to=axboe@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@canonical.com \
--cc=sedat.dilek@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).