From: Dave Jones <davej@redhat.com>
To: David Sterba <dsterba@suse.cz>
Cc: Chris Mason <chris.mason@oracle.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org, jeffm@suse.com
Subject: Re: btrfs io errors on 3.4rc1
Date: Tue, 3 Apr 2012 12:20:23 -0400 [thread overview]
Message-ID: <20120403162023.GA7227@redhat.com> (raw)
In-Reply-To: <20120403142607.GA14083@ds.suse.cz>
On Tue, Apr 03, 2012 at 04:26:07PM +0200, David Sterba wrote:
> On Mon, Apr 02, 2012 at 09:47:22PM -0400, Dave Jones wrote:
> > 49b25e0540904be0bf558b84475c69d72e4de66e is the first bad commit
> > btrfs: enhance transaction abort infrastructure
>
> Attached patch adds several debugging printks to help to track down
> where the EIOs come from. As there are no messages in syslog, it happens
> on a regular path and not after a transaction abort.
>
> I was not able to trigger the problem with either fsx or full xfstests
> suite (3.4-rc).
>
I see a lot of these ..
btrfs: __btrfs_end_transaction -EIO abored=1802201963 (no super error)
Dave
next prev parent reply other threads:[~2012-04-03 16:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 18:02 btrfs io errors on 3.4rc1 Dave Jones
2012-04-02 19:48 ` Chris Mason
2012-04-02 21:16 ` Dave Jones
2012-04-02 21:26 ` Chris Mason
2012-04-02 21:40 ` Dave Jones
2012-04-02 22:28 ` Chris Mason
2012-04-02 22:33 ` Dave Jones
2012-04-02 22:39 ` Chris Mason
2012-04-02 22:51 ` Dave Jones
2012-04-02 23:50 ` Chris Mason
2012-04-03 1:47 ` Dave Jones
2012-04-03 14:26 ` David Sterba
2012-04-03 16:20 ` Dave Jones [this message]
2012-04-03 16:33 ` David Sterba
2012-04-03 16:50 ` Dave Jones
2012-04-03 17:07 ` Dave Jones
2012-04-03 17:16 ` Dave Jones
2012-04-03 17:24 ` David Sterba
2012-04-03 19:35 ` Chris Mason
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=20120403162023.GA7227@redhat.com \
--to=davej@redhat.com \
--cc=chris.mason@oracle.com \
--cc=dsterba@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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.