On 16/02/12 00:27, Jonathan Nieder wrote: > George Barnett wrote: >> [ 317.916307] Pid: 7838, comm: umount Not tainted 2.6.32-5-openvz-amd64 #1 >> dyomin H8DGU >> [ 317.916307] RIP: 0010:[<ffffffff812ea21e>] [<ffffffff812ea21e>] >> _spin_lock_bh+0xe/0x25
>> [ 317.916307] [<ffffffffa01b97a4>] ? rpc_wake_up_queued_task+0x12/0x29 >> [sunrpc] >> [ 317.916307] [<ffffffffa01b9835>] ? rpc_killall_tasks+0x7a/0x9b [sunrpc] >> [ 317.916307] [<ffffffffa0217fed>] ? nfs_umount_begin+0x34/0x3a [nfs] >> [ 317.916307] [<ffffffff81106844>] ? sys_umount+0x11b/0x2e6 >> [ 317.916307] [<ffffffff812ec6a5>] ? do_page_fault+0x2e0/0x2fc >> [ 317.916307] [<ffffffff81010c12>] ? system_call_fastpath+0x16/0x1b Hi, FWIW, I found NFS to be very buggy before the 'feoktistov' version of the OpenVZ patchset (introduced in linux-2.6 2.6.32-31); since that version I've had no problems of this nature, and I use nfs quite heavily between OpenVZ containers. The 'dyomin' version mentioned above was based on 2.6.32.22 which I believe had some NFS issues not even specific to OpenVZ, such as kernel.org BZ#24302, and another mentioned in Debian's changelog for 2.6.32-31. Hope that helps, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f3c56e8.1010...@pyro.eu.org
