linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hendrik Friedel <hendrik@friedels.name>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfsck errors is it save to fix?
Date: Fri, 01 Nov 2013 23:29:45 +0100	[thread overview]
Message-ID: <52742B59.3060405@friedels.name> (raw)

Hello,

I have noticed that my server experiences high load average when writing 
to it. So I checked the file-system and found errors:

./btrfsck /dev/sdc1
Checking filesystem on /dev/sdc1
UUID: 989306aa-d291-4752-8477-0baf94f8c42f
checking extents
checking free space cache
checking fs roots
root 256 inode 9579 errors 100
root 256 inode 9580 errors 100
root 256 inode 14258 errors 100
root 256 inode 14259 errors 100
root 4444 inode 9579 errors 100
root 4444 inode 9580 errors 100
root 4444 inode 14258 errors 100
root 4444 inode 14259 errors 100
found 1478386534452 bytes used err is 1
total csum bytes: 3207847732
total tree bytes: 3902853120
total fs tree bytes: 38875136
total extent tree bytes: 135856128
btree space waste bytes: 411653937
file data blocks allocated: 3426722545664
  referenced 3426000965632
Btrfs v0.20-rc1-358-g194aa4a

It is a system striped over two physical disks.
Now, what concerns me is that I found no indications of problems except 
for the performance whatsoever. Nothing in the syslog.

Now that I am searching, I see this in dmesg:
[95764.899359]  [<ffffffffa00d9a59>] free_fs_root+0x99/0xa0 [btrfs]
[95764.899384]  [<ffffffffa00dd653>] 
btrfs_drop_and_free_fs_root+0x93/0xc0 [btrfs]
[95764.899408]  [<ffffffffa00dd74f>] del_fs_roots+0xcf/0x130 [btrfs]
[95764.899433]  [<ffffffffa00ddac6>] close_ctree+0x146/0x270 [btrfs]
[95764.899461]  [<ffffffffa00b4eb9>] btrfs_put_super+0x19/0x20 [btrfs]
[95764.899493]  [<ffffffffa00b754a>] btrfs_kill_super+0x1a/0x90 [btrfs]

Now the fact that the load went up indicates to me that the system 
struggled reading or writing. Can't this "struggeling" be detected and 
reported? Wouldn't this contribute to data-safety?

An the for me now more pressing question:

How can I fix the problem?


Greetings,
Hendrik

             reply	other threads:[~2013-11-01 22:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 22:29 Hendrik Friedel [this message]
2013-11-02  8:12 ` btrfsck errors is it save to fix? cwillu
2013-11-02  8:58   ` Hendrik Friedel
2013-11-04 21:14     ` Hendrik Friedel
2013-11-05  2:03       ` cwillu
2013-11-06  6:45         ` Hendrik Friedel
2013-11-07 19:16           ` Hendrik Friedel
2013-11-08 10:09             ` Duncan
2013-11-09  8:33               ` Hendrik Friedel
2013-11-11 19:06                 ` Hendrik Friedel
2013-11-11 23:58                   ` Kai Krakow
2013-11-12  7:32                     ` Duncan
2013-11-12 19:37                       ` Kai Krakow
2013-11-13 12:20                         ` Duncan
2013-11-13 12:24                         ` Duncan
2013-11-16 12:32                           ` Hendrik Friedel

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=52742B59.3060405@friedels.name \
    --to=hendrik@friedels.name \
    --cc=linux-btrfs@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).