[...] I don't use a dedicated metadata network switch but a HP 8200zl. This switch is used only for my xsan lab. 2 vlan are configurated: one about public tcp/ip network, one about metadata tcp/ip network. I'll check connections. On all my xsan nodes i have this log in /var/log/system. [...]]]>
[...] Well your MDC simply looses the connection to the Volume. It could be metadata OR it could be FC network. As told earlier, Xsan is really complicated and you should check all the connections and settings. Even order of network connections on MDC and clients matter. [...]]]>
[...] I note your link and i'll use it. But i don't understand why you are thinking the problem is with fc network and not the metadata tcp/ip network. I'm using brocade b300 and xyratex storage. They are out of matrix. But unfortunately, i didn't choice the hardware. [...]]]>
Are your Fibre Channel switch and FC cards on MDC and clients configured correctly? What FC switch you have? Make sure it is configured according http://support.apple.com/kb/TA24251 Also what type of storage you are using? Xserve RAID? Promise? 3rd party? [...]]]>
[...] Ok. i configured dns. And i configured a new volume with .Trash file created by the touch command. But the system is still having some troubles. At the begining all was ok. But after a moment, i don't know why i have the following logs in syslog of the mdc : (On my lab 192.168.2. [...]]]>
public one the metadata dns works almost like a shadow government: some services need to resolve addresses on it just in case they are needed. On Nov 4, 2009, at 9:26 AM, Fabien COMBERNOUS wrote: Vitali Bystritski wrote: [...]]]>
[...] Lol :) Sorry for my bad english. -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com <http://www.kezia.com/> *Tel: +33 (0) 467 992 986* Kezia Group]]>
[...] By "dustbin" you mean Trash folder? If yes, then take a look at the following documentation: http://support.apple.com/kb/TA24727?viewlocale=en_US]]>
Basically, you run a DNS server on the public VLAN with both entries for public and metadata IPs. For instance, according to "Apple Training Series Xsan 2 Administration: A Guide to Designing, Deploying, and Maintaining Xsan" by Robert Kite Ph.D. [...]]]>
[...] Well, i configured a zone in the dns about the metadata nerwork. Then, i destroyed the entire san. I created again a san and a volume. I mounted the new volume on a client and 2 mdc. I made a copy of an iso file from local hard drive to san. I made a copy from san to local hard drive. [...]]]>
I had crappy performance and weird hangs when the MDCs didn't have forward/reverse DNS on the private metadata network. Some people don't seem to get it, though. -- Andy Sykes IT Support Officer UCL Museums & Collections / Learning & Media Services email@hidden Museums:- Mon/Tues/Wed AM [...]]]>
[...]
I have dns configured for mdc on the data network, but not on the
metadata network. Is it necessary to configure a dns on metadata network ? This email sent to email@hidden
References:
[...]
Previous by thread:
Re: copy hang.
Index(es):
Date
Thread
Home [...]]]>Fabien COMBERNOUS wrote: [...] [...] I forgotten to say that i'm using Snow Leopard with xsan 2.2 [...] *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com <http://www.kezia.com/> *Tel: +33 (0) 467 992 986* Kezia Group]]>
Hello the list, Last week, i configured a fresh installed xsan with 2 mdc and 2 clients. Friday all was running well. From my clients i was able to access central storage and to copy big files on it. This morning, i tried to connect to a client with ARD. [...]]]>