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
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
