linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: btrfs io errors on 3.4rc1
Date: Mon, 2 Apr 2012 14:02:14 -0400	[thread overview]
Message-ID: <20120402180214.GA1830@redhat.com> (raw)

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

I tried updating my git tree..

$ gp
error: cannot open .git/FETCH_HEAD: Input/output error
$ gp
remote: Counting objects: 5101, done.
remote: Compressing objects: 100% (546/546), done.
remote: Total 3764 (delta 3233), reused 3738 (delta 3208)
Receiving objects: 100% (3764/3764), 783.19 KiB | 195 KiB/s, done.
Resolving deltas: 100% (3233/3233), completed with 831 local objects.
fatal: fsync error on '.git/objects/pack/tmp_pack_gq3edw': Input/output error
fatal: index-pack failed

I looked in dmesg, nothing out of the ordinary (disks dying etc -- plus it's happening
on two machines, so unlikely they both have hardware problems)

But anything that does writes seems to have serious issues..

$ fsx foo 
truncating to largest ever: 0x13e76
truncating to largest ever: 0x2e52c
ftruncate1: 2e52c
dotruncate: ftruncate: Input/output error
Segmentation fault (core dumped)

tried to send this email..

collect: Cannot write ./dfq32HpM1C010652 (fsync, uid=1000, gid=51): Input/output error
Error writing control file ./qfq32HpM1C010652: Input/output error


3.3 is fine.

	Dave

             reply	other threads:[~2012-04-02 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 18:02 Dave Jones [this message]
2012-04-02 19:48 ` btrfs io errors on 3.4rc1 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
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=20120402180214.GA1830@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 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).