OpenVZ Forum


Home » General » Support » [ SOLVED ] Pb with multiple identical nfs mount dir in different VEs
Re: Pb with multiple identical nfs mount dir in different VEs [message #30465 is a reply to message #30464] Mon, 26 May 2008 17:43 Go to previous messageGo to previous message
mistur is currently offline  mistur
Messages: 18
Registered: December 2007
Location: Paris
Junior Member

maratrus wrote on Mon, 26 May 2008 19:17

Quote:


ubuntu script try to remove vlan35 for kernel,



So, does the command "ifconfig eth1.35 down" cause the message "unregister_vlan_device: ERROR: Tried to remove a non-vlan device with VLAN code, name: eth1.35 priv_flags: 0" or this message doesn't appear.

You have shown strace output of that command
http://forum.openvz.org/index.php?t=msg&&th=5949& ;amp ;goto=29539#msg_29932
I haven't been able to find anything related to VLAN.


inside a VE :

#  ifdown eth1.35
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1.35/00:16:3e:02:03:1e
Sending on   LPF/eth1.35/00:16:3e:02:03:1e
Sending on   Socket/fallback
DHCPRELEASE on eth1.35 to 10.0.0.1 port 67
ERROR: trying to remove VLAN -:eth1.35:- error: Operation not permitted
#  ifup eth1.35
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Device "eth1" does not exist.
eth1 does not exist, unable to create eth1.35
run-parts: /etc/network/if-pre-up.d/vlan exited with return code 1
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP

Listening on LPF/eth1.35/00:16:3e:02:03:1e
Sending on   LPF/eth1.35/00:16:3e:02:03:1e
Sending on   Socket/fallback
DHCPDISCOVER on eth1.35 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.0.0.1
DHCPREQUEST on eth1.35 to 255.255.255.255 port 67
DHCPACK from 10.0.0.1
bound to 10.0.0.197 -- renewal in 3530590 seconds.
# ifconfig eth1.35 down
# ifconfig eth1.35 up 
# ip l set down eth1.35
# ip l set up eth1.35
#


ifdown, ifconfig and ip l set down reproduce this issue, but "unregister_vlan_device: ERROR: ..." appear only with ifdown

"/etc/init.d/networking stop" uses ifdown

so maybe it's not vlan related, and I'm working on the wrong way.

maratrus wrote on Mon, 26 May 2008 19:17

What's the difference between strace "ifconfig eth1.35 down" and "ifconfig eth1 down" (after eth1.35 rename to eth1)? Why the second case doesn't break the system? Where is the difference in strace output?


If I had the response...

there are no big diff between the 2 straces... ifconfig down does not break directly nfs export I guess, but by shutdown the interface (whatever the way to set down), something is broken in kernel land. If not, I can't see how an action inside a VE can affect another VE.

maratrus wrote on Mon, 26 May 2008 19:17

I think this sort of investigation could help us. It's the good for us to understand the difference between the "good" and the "bad" cases.


true

Yoann
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: certain iptables filter rules not working ?
Next Topic: fuse/sshfs problem
Goto Forum:
  


Current Time: Mon Aug 26 01:13:03 GMT 2024

Total time taken to generate the page: 0.03526 seconds