All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Chris Mason <chris.mason@oracle.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs io errors on 3.4rc1
Date: Mon, 2 Apr 2012 18:51:31 -0400	[thread overview]
Message-ID: <20120402225131.GB16907@redhat.com> (raw)
In-Reply-To: <20120402223919.GB18000@shiny.nikko.sjc.wayport.net>

On Mon, Apr 02, 2012 at 06:39:19PM -0400, Chris Mason wrote:
 > On Mon, Apr 02, 2012 at 06:33:50PM -0400, Dave Jones wrote:
 > > On Mon, Apr 02, 2012 at 06:28:02PM -0400, Chris Mason wrote:
 > >  
 > >  > > x86-64.
 > >  > > 
 > >  > > dmesg below.  (ignore the rpc oops, reported elsewhere, it's unrelated)
 > >  > 
 > >  > Well, there really are no btrfs messages in there at all.  Do you have
 > >  > free space for a clean copy of the btrfs partition?  Trying to figure
 > >  > out if you have a stale corruption (on two boxes seems really unlikely).
 > >  > I definitely can't reproduce it here.
 > > 
 > > Don't really have any free space for it (It's the / partition on both)
 > > 
 > > Is there a wip btrfs.fsck yet ? One of the machines is just a scratch testbox,
 > > so I'm happy to run it even if it'll potentially make things worse.
 > 
 > The current btrfsck repair mode will fix problems in the extent
 > allocation tree, but that probably isn't what you're seeing.  I'd just
 > run it read only and see if it finds any problems.
 > 
 > (You'll need the FS completely unmounted though).

I'll start a bisect later to see if I can narrow it down at least.

	Dave

  reply	other threads:[~2012-04-02 22:51 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 [this message]
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
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=20120402225131.GB16907@redhat.com \
    --to=davej@redhat.com \
    --cc=chris.mason@oracle.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.