From: David Disseldorp <ddiss@suse.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Avi Miller <avi.miller@oracle.com>,
Lists <lists@benjamindsmith.com>,
linux-btrfs@vger.kernel.org
Subject: xfstests btrfs/035 (was Re: Testing BTRFS)
Date: Wed, 12 Mar 2014 12:15:07 +0100 [thread overview]
Message-ID: <20140312121507.1f4e7f9b@plati.site> (raw)
In-Reply-To: <531F5F12.4080009@redhat.com>
Hi Eric,
On Tue, 11 Mar 2014 14:08:02 -0500, Eric Sandeen wrote:
> Indeed, testing 3.8.13-26.2.1.el6uek.x86_64 (which is, I believe,
> the kernel which Avi referred to) via xfstests, I saw
> failures on btrfs/009 and btrfs/022; then the box deadlocked
> on btrfs/024. I rebooted & resumed, then deadlocked on btrfs/030.
> Rebooted and resumed again, then panicked on btrfs/035. At that
> point I stopped.
FWIW, Liu Bo recently proposed a fix for the btrfs/035 BUG_ON():
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/33327
Cheers, David
next prev parent reply other threads:[~2014-03-12 11:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 18:18 Understanding btrfs and backups Eric Mesa
2014-03-06 21:33 ` Duncan
2014-03-07 10:13 ` Wolfgang Mader
2014-03-09 15:46 ` Duncan
2014-03-07 14:03 ` Eric Mesa
2014-03-07 15:14 ` Sander
2014-03-09 4:13 ` Chris Samuel
2014-03-09 15:30 ` Duncan
2014-03-13 8:18 ` Chris Samuel
2014-03-09 16:40 ` Duncan
2014-03-11 0:39 ` Testing BTRFS Lists
2014-03-11 1:02 ` Avi Miller
2014-03-11 19:08 ` Eric Sandeen
2014-03-11 20:30 ` Avi Miller
2014-03-12 11:15 ` David Disseldorp [this message]
2014-03-13 18:10 ` Lists
2014-03-13 20:20 ` Avi Miller
2014-03-11 13:33 ` Josef Bacik
2014-03-13 17:12 ` Understanding btrfs and backups Chris Murphy
2014-03-17 5:42 ` Understanding btrfs and backups => automatic snapshot script Marc MERLIN
2014-03-21 5:57 ` Marc MERLIN
2014-03-21 7:41 ` Duncan
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=20140312121507.1f4e7f9b@plati.site \
--to=ddiss@suse.de \
--cc=avi.miller@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@benjamindsmith.com \
--cc=sandeen@redhat.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