Bug#556231: Bug #556231

[maximilian attems <max@stro.at>]

On Tue, Feb 23, 2010 at 08:52:05AM +0100, Stephan Austermühle wrote:
> Ooops... just seconds after my mail the server panic'd while xfsdumping 
> to tape:
> 
> Kernel panic - not syncing: xfs_fs_destroy_inode: cannot reclaim 
> 0xffff8800642fcd80
> 
> Pid: 47, comm: kswapd0 Not tainted 2.6.32-2-amd64 #1
> Call trace:
>  [...] ? panic+0x86/0x141
>  [...] ? __up_write+0x12/0x45
>  [...] ? xfs_iunlock+0x42/0x7c [xfs]
>  [...] ? xfs_reclaim_inode+x094/0x12e [xfs]
>  [...] ? xfs_fs_destroy_inode+0x4b/0x4d [xfs]
>  [...] ? dispose_list+0xce/0xfe
>  [...] ? shrink_icache_memory+0x1f2/0x228
>  [...] ? shrink_slab+0xe0/0x153
>  [...] ? kswapd+0x4d9/0x683
>  [...] ? isolate_pages_global+0x0/0x20f
>  [...] ? autoremove_wake_function+0x0/0x2e
>  [...] ? kswapd+0x0/0x683
>  [...] ? kthread+0x79/0x81
>  [...] ? child_rip+0xa/0x20
>  [...] ? kthread+0x0/0x81
> 
> Looks like my issue is *not* fixed.

christoph any hint on this xfsdump to tape issue?
(2.6.30 up to 2.6.32):
http://bugs.debian.org/556231

xfsdump version is not specified. Stefan could you add that info?
output of:
dpkg -l xfsdump