From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Read errors while benchmarking
Date: Thu, 18 Jun 2009 11:03:17 +0200 [thread overview]
Message-ID: <20090618090317.GB2235@phenom2.trippelsdorf.de> (raw)
In-Reply-To: <4A3A0248.80905@wpkg.org>
On Thu, Jun 18, 2009 at 11:00:56AM +0200, Tomasz Chmielewski wrote:
> Markus Trippelsdorf wrote:
> > I'm running the latest git kernel and git btrfs-progs.
> > When I try to run some benchmarks on my btrfs partition I always get
> > read errors:
>
> (...)
>
>
> > FATAL: Failed to read file! file: 3 pos: 196608 errno = 22 ()
> > FATAL: Failed to read file! file: 13 pos: 524288 errno = 22 ()
>
> Anything interesting in dmesg?
No. Nothing.
--
Markus
next prev parent reply other threads:[~2009-06-18 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 8:24 Read errors while benchmarking Markus Trippelsdorf
2009-06-18 9:00 ` Tomasz Chmielewski
2009-06-18 9:03 ` Markus Trippelsdorf [this message]
2009-06-18 9:23 ` Yan Zheng
2009-06-24 16:53 ` Roy Sigurd Karlsbakk
2009-06-25 1:35 ` jim owens
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=20090618090317.GB2235@phenom2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=mangoo@wpkg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox