From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: at fs/btrfs/free-space-cache.c:305
Date: Fri, 04 Nov 2011 08:43:52 +0900 [thread overview]
Message-ID: <4EB32738.1010407@jp.fujitsu.com> (raw)
In-Reply-To: <20111103111927.GJ18900@shiny>
(2011/11/03 20:19), Chris Mason wrote:
> On Thu, Nov 03, 2011 at 10:25:23AM +0900, Tsutomu Itoh wrote:
>> In integration-scrub branch, following warning messages were displayed by
>> running xfstests.
>>
>> # btrfs fi sh /dev/sdd4
>> Label: none uuid: 8f28d85c-e37c-4c1b-adef-2627ca59be78
>> Total devices 2 FS bytes used 31.49MB
>> devid 1 size 9.31GB used 9.31GB path /dev/sdd4
>> devid 2 size 15.01GB used 9.29GB path /dev/sdc1
>>
>> Btrfs Btrfs v0.19
>> # mount
>> ...
>> /dev/sdd4 on /test7 type btrfs (rw,compress=lzo)
>> #
>>
>> Thanks,
>> Tsutomu
>>
>> ====================================================================================
>>
>> Nov 3 09:55:18 luna kernel: [ 939.732044] device fsid 8f28d85c-e37c-4c1b-adef-2627ca59be78 devid 1 transid 20510 /dev/sdd4
>> Nov 3 09:55:18 luna kernel: [ 939.732533] btrfs: use lzo compression
>> Nov 3 09:55:18 luna kernel: [ 939.732536] btrfs: disk space caching is enabled
>> Nov 3 09:55:18 luna kernel: [ 939.898190] ------------[ cut here ]------------
>> Nov 3 09:55:18 luna kernel: [ 939.898223] WARNING: at fs/btrfs/free-space-cache.c:305 io_ctl_map_page+0x29/0x76 [btrfs]()
>> Nov 3 09:55:18 luna kernel: [ 939.898227] Hardware name: PRIMERGY
>> Nov 3 09:55:18 luna kernel: [ 939.898229] Modules linked in: btrfs zlib_deflate crc32c libcrc32c nfsd lockd nfs_acl auth_rpcgss autofs4 sunrpc 8021q garp stp llc cpufreq_ondemand acpi_cpufreq freq_table mperf cachefiles fscache ipv6 ext3 jbd dm_mirror dm_region_hash dm_log dm_mod kvm uinput ppdev parport_pc parport sg pcspkr i2c_i801 i2c_core iTCO_wdt iTCO_vendor_support tg3 shpchp pci_hotplug i3000_edac edac_core ext4 mbcache jbd2 crc16 sd_mod crc_t10dif megaraid_sas sr_mod cdrom floppy pata_acpi ata_generic ata_piix libata scsi_mod [last unloaded: microcode]
>> Nov 3 09:55:18 luna kernel: [ 939.898291] Pid: 13337, comm: dd Not tainted 3.1.0integ-sc+ #1
>> Nov 3 09:55:18 luna kernel: [ 939.898294] Call Trace:
>> Nov 3 09:55:18 luna kernel: [ 939.898303] [<ffffffff8104b6fe>] warn_slowpath_common+0x85/0x9d
>> Nov 3 09:55:18 luna kernel: [ 939.898308] [<ffffffff8104b730>] warn_slowpath_null+0x1a/0x1c
>> Nov 3 09:55:18 luna kernel: [ 939.898328] [<ffffffffa0477507>] io_ctl_map_page+0x29/0x76 [btrfs]
>> Nov 3 09:55:18 luna kernel: [ 939.898349] [<ffffffffa0477733>] io_ctl_check_crc+0x62/0xdd [btrfs]
>
> Looks like io_ctl_read_bitmap will call io_ctl_check_crc with a mapped
> page mapped. Any chance you're able to reproduce this?
Yes.
However, because the panic that David reported occurs, I cannot reproduce
this problem though I executed xfstests again.
Thanks,
Tsutomu
next prev parent reply other threads:[~2011-11-03 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 1:25 WARNING: at fs/btrfs/free-space-cache.c:305 Tsutomu Itoh
2011-11-03 11:19 ` Chris Mason
2011-11-03 23:43 ` Tsutomu Itoh [this message]
2011-11-07 8:06 ` Tsutomu Itoh
2011-11-07 16:06 ` Chris Mason
2011-11-09 15:17 ` Josef Bacik
2011-11-09 23:38 ` Tsutomu Itoh
2011-11-10 8:36 ` Tsutomu Itoh
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=4EB32738.1010407@jp.fujitsu.com \
--to=t-itoh@jp.fujitsu.com \
--cc=chris.mason@oracle.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.