Bug#592463: [lenny] domU kernel freeze on xfs location

[Jonathan Nieder <jrnieder@gmail.com>]

Hi,

In 2010, sysadmin@campbell-lange.net wrote:

> Yesterday we had a domU PV host freeze up in a file location. The
> following log was received:
>
>     [20108008.237603] BUG: soft lockup - CPU#0 stuck for 61s! [smbd:16411]
[...]
>     [20108008.237603] Pid: 16411, comm: smbd Not tainted 2.6.26-2-xen-amd64 #1
[...]
>     [20108008.237603] Call Trace:
>     [20108008.237603]  [<ffffffffa00550d7>] ? :xfs:xfs_bmap_search_multi_extents 0x78/0xda
>     [20108008.237603]  [<ffffffffa0055194>] ? :xfs:xfs_bmap_search_extents 0x5b/0xe6
>     [20108008.237603]  [<ffffffffa005b1df>] ? :xfs:xfs_bmapi 0x26e/0xf76
>     [20108008.237603]  [<ffffffff80436b47>] ? error_exit 0x0/0x69
>     [20108008.237603]  [<ffffffff80436b47>] ? error_exit 0x0/0x69
>     [20108008.237603]  [<ffffffffa0096441>] ? :xfs:xfs_zero_eof 0xc0/0x16a
>     [20108008.237603]  [<ffffffffa0096b0e>] ? :xfs:xfs_write 0x344/0x722
>     [20108008.237603]  [<ffffffff8028a1ef>] ? do_sync_write 0xc9/0x10c
>     [20108008.237603]  [<ffffffff8020e7bc>] ? get_nsec_offset 0x9/0x2c
>     [20108008.237603]  [<ffffffff802992dc>] ? __posix_lock_file 0x3c1/0x3f6
[...]
> This domU could not be rebooted, and had to be xm destroy then
> recreated again before the filesystem was accessible again.

Thanks for reporting it, and sorry for the slow response.

Did this only happen once, or was it reproducible?  If it happened
again, on which kernel?

Sincerely,
Jonathan