linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Dave Jones <davej@redhat.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:28:02 -0400	[thread overview]
Message-ID: <20120402222802.GA18000@shiny.nikko.sjc.wayport.net> (raw)
In-Reply-To: <20120402214051.GB2487@redhat.com>

On Mon, Apr 02, 2012 at 05:40:51PM -0400, Dave Jones wrote:
> On Mon, Apr 02, 2012 at 05:26:08PM -0400, Chris Mason wrote:
>  > On Mon, Apr 02, 2012 at 05:16:22PM -0400, Dave Jones wrote:
>  > > On Mon, Apr 02, 2012 at 03:48:14PM -0400, Chris Mason wrote:
>  > >  > On Mon, Apr 02, 2012 at 02:02:14PM -0400, Dave Jones wrote:
>  > >  > > Updated to rc1 this morning, and my machines with btrfs are all freaking out..
>  > >  > > 
>  > >  > > I got this from my cron email ..
>  > >  > > 
>  > >  > > /etc/cron.daily/prelink: line 41: /var/lib/prelink/full: Input/output error
>  > >  > > cp: cannot create regular file `/var/lib/prelink/quick': Input/output error
>  > >  > > /etc/cron.daily/prelink: line 45: /var/log/prelink/prelink.log: Input/output error
>  > >  > 
>  > >  > That's not good.  Can you please try my for-linus branch against 3.3?
>  > >  > That will rules out all the shiny new btrfs code.
>  > >  > 
>  > >  > git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
>  > >  > 
>  > >  > -chris
>  > > 
>  > > Broken.
>  > > 
>  > > (17:14:52:davej@dhcp-189-232:~)$ fsx foo
>  > > truncating to largest ever: 0x13e76
>  > > truncating to largest ever: 0x2e52c
>  > > ftruncate1: 2e52c
>  > > dotruncate: ftruncate: Input/output error
>  > > Segmentation fault (core dumped)
>  > 
>  > Huh.  x86-32 or x86-64?  I know you said there were no interesting
>  > messages, but could you please send the messages you did get?
> 
> 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.

-chris


  reply	other threads:[~2012-04-02 22:28 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 [this message]
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
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=20120402222802.GA18000@shiny.nikko.sjc.wayport.net \
    --to=chris.mason@oracle.com \
    --cc=davej@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).