From: Li Zefan <lizf@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Crash in io_ctl_drop_pages after mount with csum errors
Date: Fri, 06 Jan 2012 15:17:59 +0800 [thread overview]
Message-ID: <4F06A027.3060908@cn.fujitsu.com> (raw)
In-Reply-To: <20120105164919.GP7322@twin.jikos.cz>
David Sterba wrote:
> I mounted a multi-folume fs created not-so-long ago in a 3.1 based
> kernel and mounted with v3.2-rc7-83-g115e8e7 , it crashed immediately.
> It's quite possible that the disk is to blame, it's an old 160G
> SP1614C, but syslog does not contain any error messages. I'm not sure
> whether the fs was cleanly unmounted, seems not, but anyway I do not
> expect a crash.
>
> Label: none uuid: 5f06f9eb-9736-49f7-91a2-2f45522512ef
> Total devices 4 FS bytes used 1.38GB
> devid 4 size 34.00GB used 34.00GB path /dev/sdg8
> devid 3 size 34.00GB used 34.00GB path /dev/sdg7
> devid 2 size 34.00GB used 34.00GB path /dev/sdg6
> devid 1 size 34.00GB used 34.00GB path /dev/sdg5
>
> mount options: compress-force=lzo,space_cache,autodefrag,inode_cache
>
> [ 1461.732855] btrfs: force lzo compression
> [ 1461.732876] btrfs: enabling auto defrag
> [ 1461.732893] btrfs: enabling inode map caching
> [ 1461.732907] btrfs: disk space caching is enabled
> [ 1499.796181] btrfs: csum mismatch on free space cache
> [ 1499.796266] btrfs: failed to load free space cache for block group 29360128
> [ 1499.888699] btrfs csum failed ino 18446744073709551604 off 65536 csum 2566472073 private 1925235876
> [ 1499.888826] btrfs csum failed ino 18446744073709551604 off 327680 csum 2566472073 private 1925235876
> [ 1499.906229] btrfs csum failed ino 18446744073709551604 off 0 csum 1695430581 private 1170642078
> [ 1499.906345] btrfs csum failed ino 18446744073709551604 off 262144 csum 2566472073 private 1925235876
> [ 1499.906446] btrfs csum failed ino 18446744073709551604 off 524288 csum 2566472073 private 1925235876
> [ 1499.924469] btrfs csum failed ino 18446744073709551604 off 196608 csum 2566472073 private 1925235876
> [ 1499.924574] btrfs csum failed ino 18446744073709551604 off 458752 csum 2566472073 private 1925235876
> [ 1499.946076] btrfs csum failed ino 18446744073709551604 off 131072 csum 2566472073 private 1925235876
> [ 1499.946217] btrfs csum failed ino 18446744073709551604 off 393216 csum 2566472073 private 1925235876
> [ 1499.946318] btrfs csum failed ino 18446744073709551604 off 0 csum 1695430581 private 1170642078
> [ 1499.946362] btrfs: error reading free space cache
We have inconsitent data on disk with both free space cache and free ino cache.
> [ 1499.946409] BUG: unable to handle kernel NULL pointer dereference at 0000000000000001
> [ 1499.946437] IP: [<ffffffffa0456dd7>] io_ctl_drop_pages+0x37/0x70 [btrfs]
0x01 is weired, don't know how it occured. Nevertheless we need this fix:
diff --git a/fs/btrfs/free-space-cache.c b/fs/btrfs/free-space-cache.c
index ec23d43..81771ca 100644
--- a/fs/btrfs/free-space-cache.c
+++ b/fs/btrfs/free-space-cache.c
@@ -319,9 +319,11 @@ static void io_ctl_drop_pages(struct io_ctl *io_ctl)
io_ctl_unmap_page(io_ctl);
for (i = 0; i < io_ctl->num_pages; i++) {
- ClearPageChecked(io_ctl->pages[i]);
- unlock_page(io_ctl->pages[i]);
- page_cache_release(io_ctl->pages[i]);
+ if (io_ctl->pages[i]) {
+ ClearPageChecked(io_ctl->pages[i]);
+ unlock_page(io_ctl->pages[i]);
+ page_cache_release(io_ctl->pages[i]);
+ }
}
}
I'll resend the patch along with my other pending patches for 3.3.
next prev parent reply other threads:[~2012-01-06 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 16:49 Crash in io_ctl_drop_pages after mount with csum errors David Sterba
2012-01-06 7:17 ` Li Zefan [this message]
2012-01-06 15:55 ` David Sterba
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=4F06A027.3060908@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--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 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.