OpenVZ Forum: Support » After updating to newest OpenVZ NFS seems to have a problem

Home » General » Support » After updating to newest OpenVZ NFS seems to have a problem

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

After updating to newest OpenVZ NFS seems to have a problem [message #51352]

Fri, 25 April 2014 18:32

rumburak
Messages: 2
Registered: April 2014

Junior Member

Hi,
my /vz is mounted by NFS (vers=3) and I never had any problems for years, but after updating

vzkernel-2.6.32-042stab085.20.x86_64 -> vzkernel-2.6.32-042stab088.4.x86_64
vzctl-4.6.1-1.x86_64 -> vzctl-4.7-1.x86_64

I now see the following errors on my console (CentOS 6.4) when I reboot.
The machine and the VEs seems to be OK but anyone knows what's going on here?

(Full log is attached.)

Apr 25 18:54:48 my-machine kernel: [33024.548470] ------------[ cut here ]------------
Apr 25 18:54:48 my-machine kernel: [33024.548724] WARNING: at fs/nfs/inode.c:120 nfs_clear_inode+0xa7/0xb0 [nfs]() (Not tainted)
Apr 25 18:54:48 my-machine kernel: [33024.549087] Hardware name: VMware Virtual Platform
Apr 25 18:54:48 my-machine kernel: [33024.549289] nfs_clear_inode: inode (ino: 2670533) reserved bytes: 282624
Apr 25 18:54:48 my-machine kernel: [33024.549537] Modules linked in: vzdquota vzevent nfs lockd fscache auth_rpcgss nfs_acl sunrpc vzdev ipv6 ppdev parport_pc parport e1000 vmware_balloon sg i2c_piix4 i2c_core shpchp ext4 jbd2 mbcache sd_mod crc_t10dif sr_mod cdrom vmw_pvscsi pata_acpi ata_generic ata_piix dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ploop]
Apr 25 18:54:48 my-machine kernel: [33024.553153] Pid: 7470, comm: umount.nfs veid: 0 Not tainted 2.6.32-042stab088.4 #1
Apr 25 18:54:48 my-machine kernel: [33024.554991] Call Trace:
Apr 25 18:54:48 my-machine kernel: [33024.555244] [<ffffffff81075037>] ? warn_slowpath_common+0x87/0xc0
Apr 25 18:54:48 my-machine kernel: [33024.555537] [<ffffffff81075126>] ? warn_slowpath_fmt+0x46/0x50
Apr 25 18:54:48 my-machine kernel: [33024.555833] [<ffffffffa028e317>] ? nfs_clear_inode+0xa7/0xb0 [nfs]
Apr 25 18:54:48 my-machine kernel: [33024.556181] [<ffffffff811c996c>] ? clear_inode+0xac/0x140
Apr 25 18:54:48 my-machine kernel: [33024.556454] [<ffffffff811c9a40>] ? dispose_list+0x40/0x120
Apr 25 18:54:48 my-machine kernel: [33024.556723] [<ffffffff811ca0c8>] ? invalidate_inodes_check+0x238/0x3e0
Apr 25 18:54:48 my-machine kernel: [33024.557078] [<ffffffff811ae7a2>] ? generic_shutdown_super+0x52/0x100
Apr 25 18:54:48 my-machine kernel: [33024.557379] [<ffffffff811ae8e0>] ? kill_anon_super+0x40/0x80
Apr 25 18:54:48 my-machine kernel: [33024.557666] [<ffffffffa0293345>] ? nfs_kill_super+0x25/0x40 [nfs]
Apr 25 18:54:48 my-machine kernel: [33024.557951] [<ffffffff811aeda9>] ? deactivate_super+0x79/0xa0
Apr 25 18:54:48 my-machine kernel: [33024.558292] [<ffffffff811cf4ef>] ? mntput_no_expire+0xbf/0x110
Apr 25 18:54:48 my-machine kernel: [33024.558574] [<ffffffff811d0122>] ? sys_umount+0x82/0x3d0
Apr 25 18:54:48 my-machine kernel: [33024.558841] [<ffffffff8100b102>] ? system_call_fastpath+0x16/0x1b
Apr 25 18:54:48 my-machine kernel: [33024.559185] ---[ end trace f63a15ea49efa196 ]---
Apr 25 18:54:48 my-machine kernel: [33024.559428] Tainting kernel with flag 0x9
Apr 25 18:54:48 my-machine kernel: [33024.559650] Pid: 7470, comm: umount.nfs veid: 0 Not tainted 2.6.32-042stab088.4 #1
Apr 25 18:54:48 my-machine kernel: [33024.560088] Call Trace:
Apr 25 18:54:48 my-machine kernel: [33024.560280] [<ffffffff81074ec1>] ? add_taint+0x71/0x80
Apr 25 18:54:48 my-machine kernel: [33024.560539] [<ffffffff81075044>] ? warn_slowpath_common+0x94/0xc0
Apr 25 18:54:48 my-machine kernel: [33024.560825] [<ffffffff81075126>] ? warn_slowpath_fmt+0x46/0x50
Apr 25 18:54:48 my-machine kernel: [33024.561174] [<ffffffffa028e317>] ? nfs_clear_inode+0xa7/0xb0 [nfs]
Apr 25 18:54:48 my-machine kernel: [33024.561465] [<ffffffff811c996c>] ? clear_inode+0xac/0x140
Apr 25 18:54:48 my-machine kernel: [33024.561729] [<ffffffff811c9a40>] ? dispose_list+0x40/0x120
Apr 25 18:54:48 my-machine kernel: [33024.561995] [<ffffffff811ca0c8>] ? invalidate_inodes_check+0x238/0x3e0
Apr 25 18:54:48 my-machine kernel: [33024.562346] [<ffffffff811ae7a2>] ? generic_shutdown_super+0x52/0x100
Apr 25 18:54:48 my-machine kernel: [33024.562641] [<ffffffff811ae8e0>] ? kill_anon_super+0x40/0x80
Apr 25 18:54:48 my-machine kernel: [33024.562926] [<ffffffffa0293345>] ? nfs_kill_super+0x25/0x40 [nfs]
Apr 25 18:54:48 my-machine kernel: [33024.563270] [<ffffffff811aeda9>] ? deactivate_super+0x79/0xa0
Apr 25 18:54:48 my-machine kernel: [33024.563554] [<ffffffff811cf4ef>] ? mntput_no_expire+0xbf/0x110
Apr 25 18:54:48 my-machine kernel: [33024.563831] [<ffffffff811d0122>] ? sys_umount+0x82/0x3d0
Apr 25 18:54:48 my-machine kernel: [33024.564148] [<ffffffff8100b102>] ? system_call_fastpath+0x16/0x1b

Attachment: messages.txt
(Size: 20.39KB, Downloaded 417 times)

Report message to a moderator

[Message index]

		After updating to newest OpenVZ NFS seems to have a problem By: rumburak on Fri, 25 April 2014 18:32
		Re: After updating to newest OpenVZ NFS seems to have a problem By: Paparaciz on Sat, 26 April 2014 12:44
		Re: After updating to newest OpenVZ NFS seems to have a problem By: rumburak on Sun, 27 April 2014 07:01

Previous Topic:	Cron weird behaviour (running twice)
Next Topic:	Can't add ELRepo to CentOS 6 because of OpenVZ kernel. Is it ABI Compatible?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Aug 30 17:09:25 GMT 2025

Total time taken to generate the page: 0.09499 seconds