Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Josef Bacik <JBacik@fusionio.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel 3.8.8: btrfs still crashes on boot when it can't replay a log
Date: Fri, 17 May 2013 21:51:46 -0400	[thread overview]
Message-ID: <20130518015146.GJ1765@localhost.localdomain> (raw)
In-Reply-To: <20130518012512.GD28168@merlins.org>

On Fri, May 17, 2013 at 07:25:12PM -0600, Marc MERLIN wrote:
> On Fri, May 17, 2013 at 12:54:56PM -0400, Josef Bacik wrote:
> > > If so, could you add this to the list of things to fix to make btrfs a bit
> > > less scary to others? :)
> > > (and of course more production ready, this repeated problem would kill any
> > > server it happens on)
> > 
> > This has been all fixed in 3.10.  Thanks,
> 
> This is fantastic news, thanks a lot for that.
> 
> One question left: How can I tell in a problem like below whether btrfs is
> having issues, or whether my hardware is hanging?
> When this happened below, I didn't get any SATA errors from the kernel, but
> I had to reboot to clear all those hangs (after reboot it was ok)
>

When this happens run sysrq+w so I can see everybody that is backed up, and then
file a bugzilla on bugzilla.kernel.org so I can track the issue.  Thanks,

Josef 

      reply	other threads:[~2013-05-18  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 15:09 kernel 3.8.8: btrfs still crashes on boot when it can't replay a log Marc MERLIN
2013-05-17 15:48 ` Marc MERLIN
2013-05-17 16:54 ` Josef Bacik
2013-05-18  1:25   ` Marc MERLIN
2013-05-18  1:51     ` Josef Bacik [this message]

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=20130518015146.GJ1765@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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