Re: btrfs: warn_slowpath in clean_tree_block and others
On Wed, Feb 25, 2009 at 02:26:43PM -0500, Chris Mason wrote: > [ resend with the list cc'd ] > > On Wed, 2009-02-25 at 12:50 -0600, Mitch Harder (aka DontPanic) wrote: > > I'll try to test that out. > > > > I had just noticed that some of my kernel configuration settings (not > > sure which ones) seem to affect the clean_tree_block warnings I've > > been getting, and one of my customizations is usually to configure the > > kernel for a single processor. > > > > I'll push out a patch tonight that fixes things, the code to test for a > locked buffer is just broken on UP. For now, the patch below will do: Yup, that shuts it up quite effectively. :) Thanks, Hugo. -- === Hugo Mills: h...@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- If it's December 1941 in Casablanca, what time is it --- in New York? signature.asc Description: Digital signature
Re: btrfs: warn_slowpath in clean_tree_block and others
[ resend with the list cc'd ]
On Wed, 2009-02-25 at 12:50 -0600, Mitch Harder (aka DontPanic) wrote:
> I'll try to test that out.
>
> I had just noticed that some of my kernel configuration settings (not
> sure which ones) seem to affect the clean_tree_block warnings I've
> been getting, and one of my customizations is usually to configure the
> kernel for a single processor.
>
I'll push out a patch tonight that fixes things, the code to test for a
locked buffer is just broken on UP. For now, the patch below will do:
diff --git a/fs/btrfs/locking.c b/fs/btrfs/locking.c
index 85506c4..4513ecf 100644
--- a/fs/btrfs/locking.c
+++ b/fs/btrfs/locking.c
@@ -222,6 +222,5 @@ int btrfs_tree_unlock(struct extent_buffer *eb)
int btrfs_tree_locked(struct extent_buffer *eb)
{
- return test_bit(EXTENT_BUFFER_BLOCKING, &eb->bflags) ||
- spin_is_locked(&eb->lock);
+ return 1;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs: warn_slowpath in clean_tree_block and others
On Wed, Feb 25, 2009 at 01:36:26PM -0500, Chris Mason wrote: > On Tue, 2009-02-24 at 23:02 +, Hugo Mills wrote: > > This is essentially a repost of a mail I made last week, to which I > > didn't get a reply. > > Sorry I missed replying to this one last week, thanks for resending. Not a problem. I know things go astray sometimes. > >I'm getting huge numbers of kernel warnings whilst using > > btrfs. They're all "warn_slowpath", and all seem to be in > > fs/btrfs/disk-io.c. I've included one typical example at the end of > > this mail. > > > >Kernel versions are 2.6.29-rc2, -rc4 and -rc6. > > > > The warnings look like i386, exactly what hardware is this? Is your > kernel compiled for SMP or UP? amd64 and a UP kernel: h...@vlad:linux-2.6 $ uname -a Linux vlad 2.6.29-rc6 #1 Mon Feb 23 19:53:22 GMT 2009 x86_64 GNU/Linux Hardware is an original-series Turion 64 (i.e. one core) in a Socket 745 desktop motherboard. The btrfs filesystem is in LVM-on-RAID1 in an eSATA port-multiplier storage rack. > The warning you're getting is that clean_tree_block expects this block > to be locked, and giving out a warning because it is showing up as > unlocked. > > So, hopefully you're on a UP kernel and my test for a locked spinlock is > broken in that config. OK. I can try patches if necessary. Hugo. -- === Hugo Mills: h...@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- UNIX: British manufacturer of modular shelving units. --- signature.asc Description: Digital signature
Re: btrfs: warn_slowpath in clean_tree_block and others
On Tue, 2009-02-24 at 23:02 +, Hugo Mills wrote: > This is essentially a repost of a mail I made last week, to which I > didn't get a reply. > Sorry I missed replying to this one last week, thanks for resending. >I'm getting huge numbers of kernel warnings whilst using > btrfs. They're all "warn_slowpath", and all seem to be in > fs/btrfs/disk-io.c. I've included one typical example at the end of > this mail. > >Kernel versions are 2.6.29-rc2, -rc4 and -rc6. > The warnings look like i386, exactly what hardware is this? Is your kernel compiled for SMP or UP? The warning you're getting is that clean_tree_block expects this block to be locked, and giving out a warning because it is showing up as unlocked. So, hopefully you're on a UP kernel and my test for a locked spinlock is broken in that config. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: btrfs: warn_slowpath in clean_tree_block and others
The messages attached are only "WARNING" messages. I have not been encountering a crash, nor does the data seem to get corrupted in my case (as far as I can tell). Btrfs seems to actually work fine, except for the large amount of log messages. On Wed, Feb 25, 2009 at 10:13 AM, Hugo Mills wrote: > On Wed, Feb 25, 2009 at 11:05:58AM -0500, Lee Trager wrote: >> But what are you doing to the filesystem when it crashes? How did you >> mount it? > > In my case, it's mounted with this fstab entry: > > /dev/media/scratch /media/vlad/video/video btrfs noatime,nosuid,nodev > 0 0 > > and I can trigger hundreds (literally) of these backtraces with a > single "touch /media/vlad/video/video/foo". If I encode a video to the > FS, the backtraces come in bursts at intervals of, say, 20 seconds > (it's not perfectly regular). > > Hugo. > >> On Wed, Feb 25, 2009 at 08:03:01AM -0600, Mitch Harder (aka DontPanic) wrote: >> > I've been creating a local git repository of full btrfs-unstable sources. >> > >> > I'll create a new branch off the master branch, and apply the patch >> > supplied in the Feb. 11 message to the M/L. >> > >> > I then create a kernel module based on the results in /fs/btrfs/ >> > >> > I have also tried replicating the experimental branch, and merging the >> > patch into that branch, but I get the same results. >> > >> > On Wed, Feb 25, 2009 at 12:26 AM, Lee Trager wrote: >> > > Mitch, I haven't seen any problems using BTRFS and my patch on 2.6.28 or >> > > 2.6.27, what are you doing to cause this error? Are you using the latest >> > > sources from btrfs-unstable? >> > > >> > > Lee >> > > >> > > Mitch Harder (aka DontPanic) wrote: >> > >> I have also been getting similar warnings filling up my logs. >> > >> >> > >> However, in my case, I have been experimenting with back-porting btrfs >> > >> to a 2.6.28 kernel. ?So I've been waiting for the back-porting efforts >> > >> to get a little further along. >> > >> >> > >> But I thought I'd respond in case this information helps. >> > >> >> > >> Here's an example of the warnings I've been seeing: >> > >> >> > >> [80577.151167] [ cut here ] >> > >> [80577.151169] WARNING: at >> > >> /var/tmp/portage/sys-fs/btrfs-9998/work/btrfs-9998/disk-io.c:860 >> > >> clean_tree_block+0xa4/0xb0 [btrfs]() >> > >> [80577.151172] Modules linked in: btrfs snd_pcm_oss snd_mixer_oss >> > >> snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device >> > >> ipv6 ppdev snd_intel8x0 snd_ac97_codec parport_pc nvidia(P) ac97_bus >> > >> snd_pcm snd_timer ohci_hcd ssb shpchp pci_hotplug pcmcia i2c_nforce2 >> > >> snd forcedeth sr_mod pcspkr parport i2c_core snd_page_alloc nvidia_agp >> > >> sl811_hcd pcmcia_core uhci_hcd ehci_hcd >> > >> [80577.151190] Pid: 11503, comm: cp Tainted: P ? ? ? ?W >> > >> ?2.6.28-sabayon-r10 #1 >> > >> [80577.151192] Call Trace: >> > >> [80577.151195] ?[] warn_on_slowpath+0x5f/0x90 >> > >> [80577.151203] ?[] rb_insert_color+0x77/0xe0 >> > >> [80577.151221] ?[] alloc_extent_buffer+0x1fe/0x300 [btrfs] >> > >> [80577.151238] ?[] clean_tree_block+0xa4/0xb0 [btrfs] >> > >> [80577.151253] ?[] btrfs_init_new_buffer+0x7d/0x130 [btrfs] >> > >> [80577.151269] ?[] btrfs_alloc_free_block+0x104/0x110 [btrfs] >> > >> [80577.151285] ?[] __btrfs_cow_block+0x22a/0x8b0 [btrfs] >> > >> [80577.151300] ?[] generic_bin_search+0x162/0x1c0 [btrfs] >> > >> [80577.151315] ?[] btrfs_cow_block+0x156/0x200 [btrfs] >> > >> [80577.151330] ?[] btrfs_search_slot+0x1a7/0x910 [btrfs] >> > >> [80577.151333] ?[] irq_exit+0x27/0x60 >> > >> [80577.151336] ?[] do_IRQ+0x6b/0x80 >> > >> [80577.151354] ?[] read_extent_buffer+0xd5/0x170 [btrfs] >> > >> [80577.151369] ?[] btrfs_insert_empty_items+0x6d/0x410 [btrfs] >> > >> [80577.151385] ?[] btrfs_find_block_group+0xff/0x1a0 [btrfs] >> > >> [80577.151402] ?[] btrfs_new_inode+0x18d/0x360 [btrfs] >> > >> [80577.151420] ?[] btrfs_create+0x189/0x2a0 [btrfs] >> > >> [80577.151423] ?[] security_capable+0x9/0x10 >> > >> [80577.151427] ?[] vfs_create+0xcd/0x160 >> > >> [80577.151430] ?[] do_filp_open+0x5af/0x7d0 >> > >> [80577.151433] ?[] cp_new_stat64+0xf9/0x110 >> > >> [80577.151436] ?[] do_sys_open+0x4e/0xe0 >> > >> [80577.151439] ?[] sys_open+0x2c/0x40 >> > >> [80577.151442] ?[] sysenter_do_call+0x12/0x21 >> > >> [80577.151444] ---[ end trace 79cdc48bc88dedf7 ]--- >> > >> >> > >> >> > >> On Tue, Feb 24, 2009 at 5:02 PM, Hugo Mills >> > >> wrote: >> > >> >> > >>> ? This is essentially a repost of a mail I made last week, to which I >> > >>> didn't get a reply. >> > >>> >> > >>> ? I'm getting huge numbers of kernel warnings whilst using >> > >>> btrfs. They're all "warn_slowpath", and all seem to be in >> > >>> fs/btrfs/disk-io.c. I've included one typical example at the end of >> > >>> this mail. >> > >>> >> > >>> ? Kernel versions are 2.6.29-rc2, -rc4 and -rc6. >> > >>> >> > >>> ? If I do lots of writes to my btrfs filesystem (e.g. video >> > >>> encoding), I end up with a syslog in the tens-of-megab
Re: btrfs: warn_slowpath in clean_tree_block and others
On Wed, Feb 25, 2009 at 11:05:58AM -0500, Lee Trager wrote: > But what are you doing to the filesystem when it crashes? How did you > mount it? In my case, it's mounted with this fstab entry: /dev/media/scratch /media/vlad/video/video btrfs noatime,nosuid,nodev 0 0 and I can trigger hundreds (literally) of these backtraces with a single "touch /media/vlad/video/video/foo". If I encode a video to the FS, the backtraces come in bursts at intervals of, say, 20 seconds (it's not perfectly regular). Hugo. > On Wed, Feb 25, 2009 at 08:03:01AM -0600, Mitch Harder (aka DontPanic) wrote: > > I've been creating a local git repository of full btrfs-unstable sources. > > > > I'll create a new branch off the master branch, and apply the patch > > supplied in the Feb. 11 message to the M/L. > > > > I then create a kernel module based on the results in /fs/btrfs/ > > > > I have also tried replicating the experimental branch, and merging the > > patch into that branch, but I get the same results. > > > > On Wed, Feb 25, 2009 at 12:26 AM, Lee Trager wrote: > > > Mitch, I haven't seen any problems using BTRFS and my patch on 2.6.28 or > > > 2.6.27, what are you doing to cause this error? Are you using the latest > > > sources from btrfs-unstable? > > > > > > Lee > > > > > > Mitch Harder (aka DontPanic) wrote: > > >> I have also been getting similar warnings filling up my logs. > > >> > > >> However, in my case, I have been experimenting with back-porting btrfs > > >> to a 2.6.28 kernel. ?So I've been waiting for the back-porting efforts > > >> to get a little further along. > > >> > > >> But I thought I'd respond in case this information helps. > > >> > > >> Here's an example of the warnings I've been seeing: > > >> > > >> [80577.151167] [ cut here ] > > >> [80577.151169] WARNING: at > > >> /var/tmp/portage/sys-fs/btrfs-9998/work/btrfs-9998/disk-io.c:860 > > >> clean_tree_block+0xa4/0xb0 [btrfs]() > > >> [80577.151172] Modules linked in: btrfs snd_pcm_oss snd_mixer_oss > > >> snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device > > >> ipv6 ppdev snd_intel8x0 snd_ac97_codec parport_pc nvidia(P) ac97_bus > > >> snd_pcm snd_timer ohci_hcd ssb shpchp pci_hotplug pcmcia i2c_nforce2 > > >> snd forcedeth sr_mod pcspkr parport i2c_core snd_page_alloc nvidia_agp > > >> sl811_hcd pcmcia_core uhci_hcd ehci_hcd > > >> [80577.151190] Pid: 11503, comm: cp Tainted: P ? ? ? ?W > > >> ?2.6.28-sabayon-r10 #1 > > >> [80577.151192] Call Trace: > > >> [80577.151195] ?[] warn_on_slowpath+0x5f/0x90 > > >> [80577.151203] ?[] rb_insert_color+0x77/0xe0 > > >> [80577.151221] ?[] alloc_extent_buffer+0x1fe/0x300 [btrfs] > > >> [80577.151238] ?[] clean_tree_block+0xa4/0xb0 [btrfs] > > >> [80577.151253] ?[] btrfs_init_new_buffer+0x7d/0x130 [btrfs] > > >> [80577.151269] ?[] btrfs_alloc_free_block+0x104/0x110 [btrfs] > > >> [80577.151285] ?[] __btrfs_cow_block+0x22a/0x8b0 [btrfs] > > >> [80577.151300] ?[] generic_bin_search+0x162/0x1c0 [btrfs] > > >> [80577.151315] ?[] btrfs_cow_block+0x156/0x200 [btrfs] > > >> [80577.151330] ?[] btrfs_search_slot+0x1a7/0x910 [btrfs] > > >> [80577.151333] ?[] irq_exit+0x27/0x60 > > >> [80577.151336] ?[] do_IRQ+0x6b/0x80 > > >> [80577.151354] ?[] read_extent_buffer+0xd5/0x170 [btrfs] > > >> [80577.151369] ?[] btrfs_insert_empty_items+0x6d/0x410 [btrfs] > > >> [80577.151385] ?[] btrfs_find_block_group+0xff/0x1a0 [btrfs] > > >> [80577.151402] ?[] btrfs_new_inode+0x18d/0x360 [btrfs] > > >> [80577.151420] ?[] btrfs_create+0x189/0x2a0 [btrfs] > > >> [80577.151423] ?[] security_capable+0x9/0x10 > > >> [80577.151427] ?[] vfs_create+0xcd/0x160 > > >> [80577.151430] ?[] do_filp_open+0x5af/0x7d0 > > >> [80577.151433] ?[] cp_new_stat64+0xf9/0x110 > > >> [80577.151436] ?[] do_sys_open+0x4e/0xe0 > > >> [80577.151439] ?[] sys_open+0x2c/0x40 > > >> [80577.151442] ?[] sysenter_do_call+0x12/0x21 > > >> [80577.151444] ---[ end trace 79cdc48bc88dedf7 ]--- > > >> > > >> > > >> On Tue, Feb 24, 2009 at 5:02 PM, Hugo Mills > > >> wrote: > > >> > > >>> ? This is essentially a repost of a mail I made last week, to which I > > >>> didn't get a reply. > > >>> > > >>> ? I'm getting huge numbers of kernel warnings whilst using > > >>> btrfs. They're all "warn_slowpath", and all seem to be in > > >>> fs/btrfs/disk-io.c. I've included one typical example at the end of > > >>> this mail. > > >>> > > >>> ? Kernel versions are 2.6.29-rc2, -rc4 and -rc6. > > >>> > > >>> ? If I do lots of writes to my btrfs filesystem (e.g. video > > >>> encoding), I end up with a syslog in the tens-of-megabytes range. This > > >>> makes logcheck an unhappy bunny... > > >>> > > >>> ? I don't know if this behaviour is expected, and everyone using > > >>> btrfs simply puts up with it for now, or if it's something unusual > > >>> that needs investigating. On the chance that it's the latter, I'm > > >>> reporting it here. > > >>> > > >>> ? Hugo. > > >>> > > >>> Feb 23 21:45:42 vlad kernel: [ cut
Re: btrfs: warn_slowpath in clean_tree_block and others
But what are you doing to the filesystem when it crashes? How did you mount it? Lee On Wed, Feb 25, 2009 at 08:03:01AM -0600, Mitch Harder (aka DontPanic) wrote: > I've been creating a local git repository of full btrfs-unstable sources. > > I'll create a new branch off the master branch, and apply the patch > supplied in the Feb. 11 message to the M/L. > > I then create a kernel module based on the results in /fs/btrfs/ > > I have also tried replicating the experimental branch, and merging the > patch into that branch, but I get the same results. > > On Wed, Feb 25, 2009 at 12:26 AM, Lee Trager wrote: > > Mitch, I haven't seen any problems using BTRFS and my patch on 2.6.28 or > > 2.6.27, what are you doing to cause this error? Are you using the latest > > sources from btrfs-unstable? > > > > Lee > > > > Mitch Harder (aka DontPanic) wrote: > >> I have also been getting similar warnings filling up my logs. > >> > >> However, in my case, I have been experimenting with back-porting btrfs > >> to a 2.6.28 kernel. ?So I've been waiting for the back-porting efforts > >> to get a little further along. > >> > >> But I thought I'd respond in case this information helps. > >> > >> Here's an example of the warnings I've been seeing: > >> > >> [80577.151167] [ cut here ] > >> [80577.151169] WARNING: at > >> /var/tmp/portage/sys-fs/btrfs-9998/work/btrfs-9998/disk-io.c:860 > >> clean_tree_block+0xa4/0xb0 [btrfs]() > >> [80577.151172] Modules linked in: btrfs snd_pcm_oss snd_mixer_oss > >> snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device > >> ipv6 ppdev snd_intel8x0 snd_ac97_codec parport_pc nvidia(P) ac97_bus > >> snd_pcm snd_timer ohci_hcd ssb shpchp pci_hotplug pcmcia i2c_nforce2 > >> snd forcedeth sr_mod pcspkr parport i2c_core snd_page_alloc nvidia_agp > >> sl811_hcd pcmcia_core uhci_hcd ehci_hcd > >> [80577.151190] Pid: 11503, comm: cp Tainted: P ? ? ? ?W > >> ?2.6.28-sabayon-r10 #1 > >> [80577.151192] Call Trace: > >> [80577.151195] ?[] warn_on_slowpath+0x5f/0x90 > >> [80577.151203] ?[] rb_insert_color+0x77/0xe0 > >> [80577.151221] ?[] alloc_extent_buffer+0x1fe/0x300 [btrfs] > >> [80577.151238] ?[] clean_tree_block+0xa4/0xb0 [btrfs] > >> [80577.151253] ?[] btrfs_init_new_buffer+0x7d/0x130 [btrfs] > >> [80577.151269] ?[] btrfs_alloc_free_block+0x104/0x110 [btrfs] > >> [80577.151285] ?[] __btrfs_cow_block+0x22a/0x8b0 [btrfs] > >> [80577.151300] ?[] generic_bin_search+0x162/0x1c0 [btrfs] > >> [80577.151315] ?[] btrfs_cow_block+0x156/0x200 [btrfs] > >> [80577.151330] ?[] btrfs_search_slot+0x1a7/0x910 [btrfs] > >> [80577.151333] ?[] irq_exit+0x27/0x60 > >> [80577.151336] ?[] do_IRQ+0x6b/0x80 > >> [80577.151354] ?[] read_extent_buffer+0xd5/0x170 [btrfs] > >> [80577.151369] ?[] btrfs_insert_empty_items+0x6d/0x410 [btrfs] > >> [80577.151385] ?[] btrfs_find_block_group+0xff/0x1a0 [btrfs] > >> [80577.151402] ?[] btrfs_new_inode+0x18d/0x360 [btrfs] > >> [80577.151420] ?[] btrfs_create+0x189/0x2a0 [btrfs] > >> [80577.151423] ?[] security_capable+0x9/0x10 > >> [80577.151427] ?[] vfs_create+0xcd/0x160 > >> [80577.151430] ?[] do_filp_open+0x5af/0x7d0 > >> [80577.151433] ?[] cp_new_stat64+0xf9/0x110 > >> [80577.151436] ?[] do_sys_open+0x4e/0xe0 > >> [80577.151439] ?[] sys_open+0x2c/0x40 > >> [80577.151442] ?[] sysenter_do_call+0x12/0x21 > >> [80577.151444] ---[ end trace 79cdc48bc88dedf7 ]--- > >> > >> > >> On Tue, Feb 24, 2009 at 5:02 PM, Hugo Mills > >> wrote: > >> > >>> ? This is essentially a repost of a mail I made last week, to which I > >>> didn't get a reply. > >>> > >>> ? I'm getting huge numbers of kernel warnings whilst using > >>> btrfs. They're all "warn_slowpath", and all seem to be in > >>> fs/btrfs/disk-io.c. I've included one typical example at the end of > >>> this mail. > >>> > >>> ? Kernel versions are 2.6.29-rc2, -rc4 and -rc6. > >>> > >>> ? If I do lots of writes to my btrfs filesystem (e.g. video > >>> encoding), I end up with a syslog in the tens-of-megabytes range. This > >>> makes logcheck an unhappy bunny... > >>> > >>> ? I don't know if this behaviour is expected, and everyone using > >>> btrfs simply puts up with it for now, or if it's something unusual > >>> that needs investigating. On the chance that it's the latter, I'm > >>> reporting it here. > >>> > >>> ? Hugo. > >>> > >>> Feb 23 21:45:42 vlad kernel: [ cut here ] > >>> Feb 23 21:45:42 vlad kernel: WARNING: at fs/btrfs/disk-io.c:815 > >>> clean_tree_block+0x9d/0xbb [btrfs]() > >>> Feb 23 21:45:42 vlad kernel: Hardware name: System Product Name > >>> Feb 23 21:45:42 vlad kernel: Modules linked in: tun ext3 jbd btrfs > >>> zlib_deflate tcp_diag inet_diag kqemu cpufreq_userspace ipv6 nfsd nfs > >>> lockd nfs_acl auth_rpcgss sunrpc af_packet bridge stp llc xfs exportfs > >>> it87 hwmon_vid powernow_k8 sbp2 ieee1394 ide_generic ide_gd_mod > >>> ide_cd_mod pcspkr evdev k8temp hwmon i2c_viapro i2c_core button dm_mirror > >>> dm_region_hash dm_log dm_snapshot dm_mod rai
Re: btrfs: warn_slowpath in clean_tree_block and others
Mitch, I haven't seen any problems using BTRFS and my patch on 2.6.28 or 2.6.27, what are you doing to cause this error? Are you using the latest sources from btrfs-unstable? Lee Mitch Harder (aka DontPanic) wrote: > I have also been getting similar warnings filling up my logs. > > However, in my case, I have been experimenting with back-porting btrfs > to a 2.6.28 kernel. So I've been waiting for the back-porting efforts > to get a little further along. > > But I thought I'd respond in case this information helps. > > Here's an example of the warnings I've been seeing: > > [80577.151167] [ cut here ] > [80577.151169] WARNING: at > /var/tmp/portage/sys-fs/btrfs-9998/work/btrfs-9998/disk-io.c:860 > clean_tree_block+0xa4/0xb0 [btrfs]() > [80577.151172] Modules linked in: btrfs snd_pcm_oss snd_mixer_oss > snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device > ipv6 ppdev snd_intel8x0 snd_ac97_codec parport_pc nvidia(P) ac97_bus > snd_pcm snd_timer ohci_hcd ssb shpchp pci_hotplug pcmcia i2c_nforce2 > snd forcedeth sr_mod pcspkr parport i2c_core snd_page_alloc nvidia_agp > sl811_hcd pcmcia_core uhci_hcd ehci_hcd > [80577.151190] Pid: 11503, comm: cp Tainted: PW 2.6.28-sabayon-r10 #1 > [80577.151192] Call Trace: > [80577.151195] [] warn_on_slowpath+0x5f/0x90 > [80577.151203] [] rb_insert_color+0x77/0xe0 > [80577.151221] [] alloc_extent_buffer+0x1fe/0x300 [btrfs] > [80577.151238] [] clean_tree_block+0xa4/0xb0 [btrfs] > [80577.151253] [] btrfs_init_new_buffer+0x7d/0x130 [btrfs] > [80577.151269] [] btrfs_alloc_free_block+0x104/0x110 [btrfs] > [80577.151285] [] __btrfs_cow_block+0x22a/0x8b0 [btrfs] > [80577.151300] [] generic_bin_search+0x162/0x1c0 [btrfs] > [80577.151315] [] btrfs_cow_block+0x156/0x200 [btrfs] > [80577.151330] [] btrfs_search_slot+0x1a7/0x910 [btrfs] > [80577.151333] [] irq_exit+0x27/0x60 > [80577.151336] [] do_IRQ+0x6b/0x80 > [80577.151354] [] read_extent_buffer+0xd5/0x170 [btrfs] > [80577.151369] [] btrfs_insert_empty_items+0x6d/0x410 [btrfs] > [80577.151385] [] btrfs_find_block_group+0xff/0x1a0 [btrfs] > [80577.151402] [] btrfs_new_inode+0x18d/0x360 [btrfs] > [80577.151420] [] btrfs_create+0x189/0x2a0 [btrfs] > [80577.151423] [] security_capable+0x9/0x10 > [80577.151427] [] vfs_create+0xcd/0x160 > [80577.151430] [] do_filp_open+0x5af/0x7d0 > [80577.151433] [] cp_new_stat64+0xf9/0x110 > [80577.151436] [] do_sys_open+0x4e/0xe0 > [80577.151439] [] sys_open+0x2c/0x40 > [80577.151442] [] sysenter_do_call+0x12/0x21 > [80577.151444] ---[ end trace 79cdc48bc88dedf7 ]--- > > > On Tue, Feb 24, 2009 at 5:02 PM, Hugo Mills wrote: > >> This is essentially a repost of a mail I made last week, to which I >> didn't get a reply. >> >> I'm getting huge numbers of kernel warnings whilst using >> btrfs. They're all "warn_slowpath", and all seem to be in >> fs/btrfs/disk-io.c. I've included one typical example at the end of >> this mail. >> >> Kernel versions are 2.6.29-rc2, -rc4 and -rc6. >> >> If I do lots of writes to my btrfs filesystem (e.g. video >> encoding), I end up with a syslog in the tens-of-megabytes range. This >> makes logcheck an unhappy bunny... >> >> I don't know if this behaviour is expected, and everyone using >> btrfs simply puts up with it for now, or if it's something unusual >> that needs investigating. On the chance that it's the latter, I'm >> reporting it here. >> >> Hugo. >> >> Feb 23 21:45:42 vlad kernel: [ cut here ] >> Feb 23 21:45:42 vlad kernel: WARNING: at fs/btrfs/disk-io.c:815 >> clean_tree_block+0x9d/0xbb [btrfs]() >> Feb 23 21:45:42 vlad kernel: Hardware name: System Product Name >> Feb 23 21:45:42 vlad kernel: Modules linked in: tun ext3 jbd btrfs >> zlib_deflate tcp_diag inet_diag kqemu cpufreq_userspace ipv6 nfsd nfs lockd >> nfs_acl auth_rpcgss sunrpc af_packet bridge stp llc xfs exportfs it87 >> hwmon_vid powernow_k8 sbp2 ieee1394 ide_generic ide_gd_mod ide_cd_mod pcspkr >> evdev k8temp hwmon i2c_viapro i2c_core button dm_mirror dm_region_hash >> dm_log dm_snapshot dm_mod raid1 md_mod usbhid usb_storage libusual sg sr_mod >> cdrom via82cxxx floppy via_rhine mii ehci_hcd uhci_hcd usbcore pata_via >> ide_pci_generic ide_core sd_mod thermal processor fan unix >> Feb 23 21:45:42 vlad kernel: Pid: 27034, comm: hdparm Tainted: GW >> 2.6.29-rc4 #1 >> Feb 23 21:45:42 vlad kernel: Call Trace: >> Feb 23 21:45:42 vlad kernel: [] warn_slowpath+0xd8/0x111 >> Feb 23 21:45:42 vlad kernel: [] >> radix_tree_insert+0xd7/0x19f >> Feb 23 21:45:42 vlad kernel: [] >> add_to_page_cache_locked+0x52/0x9e >> Feb 23 21:45:42 vlad kernel: [] >> add_to_page_cache_lru+0x40/0x58 >> Feb 23 21:45:42 vlad kernel: [] >> find_or_create_page+0x62/0x88 >> Feb 23 21:45:42 vlad kernel: [] >> alloc_extent_buffer+0x268/0x2ec [btrfs] >> Feb 23 21:45:42 vlad kernel: [] clean_tree_block+0x9d/0xbb >> [btrfs] >> Feb 23 21:45:42 vlad kernel: [] >> btrfs_init_new_buffer+0x99/0xf3 [btrf
Re: btrfs: warn_slowpath in clean_tree_block and others
I have also been getting similar warnings filling up my logs. However, in my case, I have been experimenting with back-porting btrfs to a 2.6.28 kernel. So I've been waiting for the back-porting efforts to get a little further along. But I thought I'd respond in case this information helps. Here's an example of the warnings I've been seeing: [80577.151167] [ cut here ] [80577.151169] WARNING: at /var/tmp/portage/sys-fs/btrfs-9998/work/btrfs-9998/disk-io.c:860 clean_tree_block+0xa4/0xb0 [btrfs]() [80577.151172] Modules linked in: btrfs snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device ipv6 ppdev snd_intel8x0 snd_ac97_codec parport_pc nvidia(P) ac97_bus snd_pcm snd_timer ohci_hcd ssb shpchp pci_hotplug pcmcia i2c_nforce2 snd forcedeth sr_mod pcspkr parport i2c_core snd_page_alloc nvidia_agp sl811_hcd pcmcia_core uhci_hcd ehci_hcd [80577.151190] Pid: 11503, comm: cp Tainted: PW 2.6.28-sabayon-r10 #1 [80577.151192] Call Trace: [80577.151195] [] warn_on_slowpath+0x5f/0x90 [80577.151203] [] rb_insert_color+0x77/0xe0 [80577.151221] [] alloc_extent_buffer+0x1fe/0x300 [btrfs] [80577.151238] [] clean_tree_block+0xa4/0xb0 [btrfs] [80577.151253] [] btrfs_init_new_buffer+0x7d/0x130 [btrfs] [80577.151269] [] btrfs_alloc_free_block+0x104/0x110 [btrfs] [80577.151285] [] __btrfs_cow_block+0x22a/0x8b0 [btrfs] [80577.151300] [] generic_bin_search+0x162/0x1c0 [btrfs] [80577.151315] [] btrfs_cow_block+0x156/0x200 [btrfs] [80577.151330] [] btrfs_search_slot+0x1a7/0x910 [btrfs] [80577.151333] [] irq_exit+0x27/0x60 [80577.151336] [] do_IRQ+0x6b/0x80 [80577.151354] [] read_extent_buffer+0xd5/0x170 [btrfs] [80577.151369] [] btrfs_insert_empty_items+0x6d/0x410 [btrfs] [80577.151385] [] btrfs_find_block_group+0xff/0x1a0 [btrfs] [80577.151402] [] btrfs_new_inode+0x18d/0x360 [btrfs] [80577.151420] [] btrfs_create+0x189/0x2a0 [btrfs] [80577.151423] [] security_capable+0x9/0x10 [80577.151427] [] vfs_create+0xcd/0x160 [80577.151430] [] do_filp_open+0x5af/0x7d0 [80577.151433] [] cp_new_stat64+0xf9/0x110 [80577.151436] [] do_sys_open+0x4e/0xe0 [80577.151439] [] sys_open+0x2c/0x40 [80577.151442] [] sysenter_do_call+0x12/0x21 [80577.151444] ---[ end trace 79cdc48bc88dedf7 ]--- On Tue, Feb 24, 2009 at 5:02 PM, Hugo Mills wrote: > This is essentially a repost of a mail I made last week, to which I > didn't get a reply. > > I'm getting huge numbers of kernel warnings whilst using > btrfs. They're all "warn_slowpath", and all seem to be in > fs/btrfs/disk-io.c. I've included one typical example at the end of > this mail. > > Kernel versions are 2.6.29-rc2, -rc4 and -rc6. > > If I do lots of writes to my btrfs filesystem (e.g. video > encoding), I end up with a syslog in the tens-of-megabytes range. This > makes logcheck an unhappy bunny... > > I don't know if this behaviour is expected, and everyone using > btrfs simply puts up with it for now, or if it's something unusual > that needs investigating. On the chance that it's the latter, I'm > reporting it here. > > Hugo. > > Feb 23 21:45:42 vlad kernel: [ cut here ] > Feb 23 21:45:42 vlad kernel: WARNING: at fs/btrfs/disk-io.c:815 > clean_tree_block+0x9d/0xbb [btrfs]() > Feb 23 21:45:42 vlad kernel: Hardware name: System Product Name > Feb 23 21:45:42 vlad kernel: Modules linked in: tun ext3 jbd btrfs > zlib_deflate tcp_diag inet_diag kqemu cpufreq_userspace ipv6 nfsd nfs lockd > nfs_acl auth_rpcgss sunrpc af_packet bridge stp llc xfs exportfs it87 > hwmon_vid powernow_k8 sbp2 ieee1394 ide_generic ide_gd_mod ide_cd_mod pcspkr > evdev k8temp hwmon i2c_viapro i2c_core button dm_mirror dm_region_hash dm_log > dm_snapshot dm_mod raid1 md_mod usbhid usb_storage libusual sg sr_mod cdrom > via82cxxx floppy via_rhine mii ehci_hcd uhci_hcd usbcore pata_via > ide_pci_generic ide_core sd_mod thermal processor fan unix > Feb 23 21:45:42 vlad kernel: Pid: 27034, comm: hdparm Tainted: G W > 2.6.29-rc4 #1 > Feb 23 21:45:42 vlad kernel: Call Trace: > Feb 23 21:45:42 vlad kernel: [] warn_slowpath+0xd8/0x111 > Feb 23 21:45:42 vlad kernel: [] radix_tree_insert+0xd7/0x19f > Feb 23 21:45:42 vlad kernel: [] > add_to_page_cache_locked+0x52/0x9e > Feb 23 21:45:42 vlad kernel: [] > add_to_page_cache_lru+0x40/0x58 > Feb 23 21:45:42 vlad kernel: [] > find_or_create_page+0x62/0x88 > Feb 23 21:45:42 vlad kernel: [] > alloc_extent_buffer+0x268/0x2ec [btrfs] > Feb 23 21:45:42 vlad kernel: [] clean_tree_block+0x9d/0xbb > [btrfs] > Feb 23 21:45:42 vlad kernel: [] > btrfs_init_new_buffer+0x99/0xf3 [btrfs] > Feb 23 21:45:42 vlad kernel: [] > btrfs_alloc_free_block+0x83/0x8c [btrfs] > Feb 23 21:45:42 vlad kernel: [] > __btrfs_cow_block+0x1ff/0x87e [btrfs] > Feb 23 21:45:42 vlad kernel: [] btrfs_cow_block+0x1e7/0x1f6 > [btrfs] > Feb 23 21:45:42 vlad kernel: [] > __alloc_pages_internal+0xd2/0x3ec > Feb 23 21:45:42 vlad kernel: [] > btrfs_search_slot+0x36f/0x99b [bt
btrfs: warn_slowpath in clean_tree_block and others
This is essentially a repost of a mail I made last week, to which I didn't get a reply. I'm getting huge numbers of kernel warnings whilst using btrfs. They're all "warn_slowpath", and all seem to be in fs/btrfs/disk-io.c. I've included one typical example at the end of this mail. Kernel versions are 2.6.29-rc2, -rc4 and -rc6. If I do lots of writes to my btrfs filesystem (e.g. video encoding), I end up with a syslog in the tens-of-megabytes range. This makes logcheck an unhappy bunny... I don't know if this behaviour is expected, and everyone using btrfs simply puts up with it for now, or if it's something unusual that needs investigating. On the chance that it's the latter, I'm reporting it here. Hugo. Feb 23 21:45:42 vlad kernel: [ cut here ] Feb 23 21:45:42 vlad kernel: WARNING: at fs/btrfs/disk-io.c:815 clean_tree_block+0x9d/0xbb [btrfs]() Feb 23 21:45:42 vlad kernel: Hardware name: System Product Name Feb 23 21:45:42 vlad kernel: Modules linked in: tun ext3 jbd btrfs zlib_deflate tcp_diag inet_diag kqemu cpufreq_userspace ipv6 nfsd nfs lockd nfs_acl auth_rpcgss sunrpc af_packet bridge stp llc xfs exportfs it87 hwmon_vid powernow_k8 sbp2 ieee1394 ide_generic ide_gd_mod ide_cd_mod pcspkr evdev k8temp hwmon i2c_viapro i2c_core button dm_mirror dm_region_hash dm_log dm_snapshot dm_mod raid1 md_mod usbhid usb_storage libusual sg sr_mod cdrom via82cxxx floppy via_rhine mii ehci_hcd uhci_hcd usbcore pata_via ide_pci_generic ide_core sd_mod thermal processor fan unix Feb 23 21:45:42 vlad kernel: Pid: 27034, comm: hdparm Tainted: GW 2.6.29-rc4 #1 Feb 23 21:45:42 vlad kernel: Call Trace: Feb 23 21:45:42 vlad kernel: [] warn_slowpath+0xd8/0x111 Feb 23 21:45:42 vlad kernel: [] radix_tree_insert+0xd7/0x19f Feb 23 21:45:42 vlad kernel: [] add_to_page_cache_locked+0x52/0x9e Feb 23 21:45:42 vlad kernel: [] add_to_page_cache_lru+0x40/0x58 Feb 23 21:45:42 vlad kernel: [] find_or_create_page+0x62/0x88 Feb 23 21:45:42 vlad kernel: [] alloc_extent_buffer+0x268/0x2ec [btrfs] Feb 23 21:45:42 vlad kernel: [] clean_tree_block+0x9d/0xbb [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_init_new_buffer+0x99/0xf3 [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_alloc_free_block+0x83/0x8c [btrfs] Feb 23 21:45:42 vlad kernel: [] __btrfs_cow_block+0x1ff/0x87e [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_cow_block+0x1e7/0x1f6 [btrfs] Feb 23 21:45:42 vlad kernel: [] __alloc_pages_internal+0xd2/0x3ec Feb 23 21:45:42 vlad kernel: [] btrfs_search_slot+0x36f/0x99b [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_insert_empty_items+0x7f/0x49d [btrfs] Feb 23 21:45:42 vlad kernel: [] __btrfs_alloc_reserved_extent+0x19f/0x2bb [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_alloc_extent+0x77/0xa2 [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_alloc_free_block+0x64/0x8c [btrfs] Feb 23 21:45:42 vlad kernel: [] __btrfs_cow_block+0x1ff/0x87e [btrfs] Feb 23 21:45:42 vlad kernel: [] finish_current_insert+0x514/0x528 [btrfs] Feb 23 21:45:42 vlad kernel: [] del_pending_extents+0xa5/0x33d [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_cow_block+0x1e7/0x1f6 [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_commit_tree_roots+0x53/0x1ba [btrfs] Feb 23 21:45:42 vlad kernel: [] schedule_timeout+0xa1/0xbc Feb 23 21:45:42 vlad kernel: [] btrfs_commit_transaction+0x322/0x6e5 [btrfs] Feb 23 21:45:42 vlad kernel: [] autoremove_wake_function+0x0/0x2e Feb 23 21:45:42 vlad kernel: [] join_transaction+0x129/0x147 [btrfs] Feb 23 21:45:42 vlad kernel: [] btrfs_sync_fs+0x70/0x78 [btrfs] Feb 23 21:45:42 vlad kernel: [] sync_filesystems+0xa8/0xde Feb 23 21:45:42 vlad kernel: [] do_sync+0x25/0x50 Feb 23 21:45:42 vlad kernel: [] sys_sync+0xe/0x13 Feb 23 21:45:42 vlad kernel: [] system_call_fastpath+0x16/0x1b Feb 23 21:45:42 vlad kernel: ---[ end trace a315082d564863a6 ]--- -- === Hugo Mills: h...@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- Eighth Army Push Bottles Up Germans -- WWII newspaper --- headline (possibly apocryphal) signature.asc Description: Digital signature
warn_slowpath in clean_tree_block
I've just started playing with Btrfs, and I'm getting a log full of kernel warnings that look something like this: Feb 16 09:02:17 vlad kernel: [ cut here ] Feb 16 09:02:17 vlad kernel: WARNING: at fs/btrfs/disk-io.c:815 clean_tree_block+0x9d/0xbb [btrfs]() Feb 16 09:02:17 vlad kernel: Hardware name: System Product Name Feb 16 09:02:17 vlad kernel: Modules linked in: btrfs zlib_deflate tcp_diag inet_diag kqemu cpufreq_userspace ipv6 nfsd nfs lockd nfs_acl auth_rpcgss sunrpc af_packet bridge stp llc xfs exportfs it87 hwmon_vid powernow_k8 sbp2 ieee1394 ide_generic ide_gd_mod ide_cd_mod pcspkr evdev k8temp hwmon i2c_viapro i2c_core button dm_mirror dm_region_hash dm_log dm_snapshot dm_mod raid1 md_mod usbhid usb_storage libusual sg sr_mod cdrom via82cxxx floppy via_rhine mii ehci_hcd uhci_hcd usbcore pata_via ide_pci_generic ide_core sd_mod thermal processor fan unix Feb 16 09:02:17 vlad kernel: Pid: 24129, comm: btrfs-endio-wri Tainted: G W 2.6.29-rc4 #1 Feb 16 09:02:17 vlad kernel: Call Trace: Feb 16 09:02:17 vlad kernel: [] warn_slowpath+0xd8/0x111 Feb 16 09:02:17 vlad kernel: [] __alloc_pages_internal+0xd2/0x3ec Feb 16 09:02:17 vlad kernel: [] add_to_page_cache_locked+0x52/0x9e Feb 16 09:02:17 vlad kernel: [] add_to_page_cache_lru+0x40/0x58 Feb 16 09:02:17 vlad kernel: [] find_or_create_page+0x62/0x88 Feb 16 09:02:17 vlad kernel: [] rb_insert_color+0xba/0xe2 Feb 16 09:02:17 vlad kernel: [] alloc_extent_buffer+0x268/0x2ec [btrfs] Feb 16 09:02:17 vlad kernel: [] clean_tree_block+0x9d/0xbb [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_init_new_buffer+0x99/0xf3 [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_alloc_free_block+0x83/0x8c [btrfs] Feb 16 09:02:17 vlad kernel: [] split_leaf+0x159/0xa0a [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_item_offset+0xb3/0xbe [btrfs] Feb 16 09:02:17 vlad kernel: [] leaf_space_used+0xb5/0xe8 [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_search_slot+0x917/0x99b [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_drop_extents+0xa75/0xab3 [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_insert_empty_items+0x7f/0x49d [btrfs] Feb 16 09:02:17 vlad kernel: [] insert_reserved_file_extent+0xd9/0x230 [btrfs] Feb 16 09:02:17 vlad kernel: [] set_extent_bit+0x220/0x277 [btrfs] Feb 16 09:02:17 vlad kernel: [] lock_extent+0x46/0x95 [btrfs] Feb 16 09:02:17 vlad kernel: [] btrfs_finish_ordered_io+0xfe/0x198 [btrfs] Feb 16 09:02:17 vlad kernel: [] end_bio_extent_writepage+0xa9/0x1b1 [btrfs] Feb 16 09:02:17 vlad kernel: [] worker_loop+0x5f/0x15e [btrfs] Feb 16 09:02:17 vlad kernel: [] worker_loop+0x0/0x15e [btrfs] Feb 16 09:02:17 vlad kernel: [] worker_loop+0x0/0x15e [btrfs] Feb 16 09:02:17 vlad kernel: [] kthread+0x47/0x73 Feb 16 09:02:17 vlad kernel: [] child_rip+0xa/0x20 Feb 16 09:02:17 vlad kernel: [] kthread+0x0/0x73 Feb 16 09:02:17 vlad kernel: [] child_rip+0x0/0x20 Feb 16 09:02:17 vlad kernel: ---[ end trace a315082d5647b979 ]--- They're not all identical -- there are bits in the middle of the trace that change. They tend to arrive in groups of 4-8 warnings very close together, separated by 15-20 seconds without a warning. The workload was encoding a video from another filesystem, onto the Btrfs filesystem. It's quiet when there's nothing accessing the filesystem. The filesystem is 19GiB in size, residing on LVM-on-RAID-1 on a 2.6.29-rc4 kernel. It was created on 2.6.29-rc3, 20GiB in size using btrfs tools 0.18-ge3b0f66, and shrunk online to its current size. I haven't found any similar reports on the mailing list, which means either I've got something unusual, or something so blindingly expected that nobody's bothered to mention it. I suspect the latter, but I'm reporting it in case it's the former. Hugo. -- === Hugo Mills: h...@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- "You got very nice eyes, Deedee. Never noticed them --- before. They real?" signature.asc Description: Digital signature
