Sorry, cannot find an updated 2.6.30-2-amd64 on unstable. Do you mean
2.6.32-2-amd64?

On Sun, Feb 14, 2010 at 12:00:41PM +0100, Stephan Austermühle wrote:
> Sorry, cannot find an updated 2.6.30-2-amd64 on unstable. Do you
> mean 2.6.32-2-amd64?

Yes, please try that version.

Cheers,
Moritz









--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100214113704.GA3368@galadriel.inutil.org">http://lists.debian.org/20100214113704.GA3368@galadriel.inutil.org

On Sun, Feb 14, 2010 at 12:00:41PM +0100, Stephan Austermühle wrote:
> Sorry, cannot find an updated 2.6.30-2-amd64 on unstable. Do you mean
> 2.6.32-2-amd64?

yes of course, sorry for the typo. 2.6.30 is dead.






--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100214212349.GI9624@baikonur.stro.at">http://lists.debian.org/20100214212349.GI9624@baikonur.stro.at

No issues so far with 2.6.32. xfsdump to tape seems to work better now,
i.e. no panics.


I think we can close this bug.

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.

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



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100223103545.GB15228@baikonur.stro.at">http://lists.debian.org/20100223103545.GB15228@baikonur.stro.at

Hi all,

Am 23.02.2010 11:35, schrieb maximilian attems:


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


Here we go...

# dpkg -l xfsdump
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)

||/ Name Version Description
+++-=================-=================-==================================================
ii xfsdump 3.0.2 Administrative utilities for the
XFS filesystem



Best regards,

Stephan

On Tue, Feb 23, 2010 at 11:55:57AM +0100, Stephan Austermühle wrote:
> Hi all,
>
> Am 23.02.2010 11:35, schrieb maximilian attems:
>
> >xfsdump version is not specified. Stefan could you add that info?
> >output of:
> >dpkg -l xfsdump
>
> Here we go...
>
> # dpkg -l xfsdump
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> uppercase=bad)
> ||/ Name Version Description
> +++-=================-=================-==================================================
> ii xfsdump 3.0.2 Administrative utilities for
> the XFS filesystem

2.6.32.12 has introduced lots of xfs bugfixes. Please try the current
2.6.32-13 kernel from unstable. If the error can still be reproduced
it should be reported upstream at bugzilla.kernel.org

Cheers,
Moritz




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100522174219.GA28811@galadriel.inutil.org">http://lists.debian.org/20100522174219.GA28811@galadriel.inutil.org

Hi all,

Am 22.05.2010 19:42, schrieb Moritz Muehlenhoff:

> 2.6.32.12 has introduced lots of xfs bugfixes. Please try the current
> 2.6.32-13 kernel from unstable. If the error can still be reproduced
> it should be reported upstream at bugzilla.kernel.org

Looks like my issue has been solved with 2.6.32-13. At least I was not
able to reproduce the error within three attempts anymore (every
complete xfsdump run takes many, many hours).

Best regards,

Stephan