shadow_copy2 requires wide links enabled

[Paul B. Henson]

On 1/7/2011 3:36 AM, Volker Lendecke wrote:

 > We have made changes to fix this. The new CONNECTPATH
 > operation is made to fix it, and it is present in 3.5. The
 > version a customer of mine is using is definitely regularly
 > tested for this feature, but that is 3.4 with backported
 > patches. It is surprising that it does not work for you in
 > 3.5.5, that definitely has those patches. We need more logs.

Hmm, as I mentioned, it is not a stock 3.5.5; it's the Oracle (nee Sun) 
version with their patches, and I'm using the 3.6 version of 
shadow_copy2. I wouldn't imagine the Oracle patches would affect it, 
they're mostly to make it work with their ldap and kerberos 
implementation. However, I'm using the 3.6 shadow_copy2 for the format 
option, in particular I have it set to "backup-%Y.%m.%d-%H.%M.%S" rather 
than the default "@GMT...", although it seems the module eventually 
turned it into that format. An initial wild guess is that maybe 
something somewhere assumes that shadow copy paths on the underlying 
filesystem are always in the @GMT format.

I'll take a look and see if anything jumps out; what log level would be 
best to submit? I have trouble finding anything between "not enough 
detail" and "so much detail my head explodes" ;).

 > But be aware, the shadow_copy2 module is really HELL to
 > debug.

Oh joy :). At least I have it working, but wide links enabled is 
definitely not preferable, even with the UNIX extensions disabled; the 
filesystems are also shared via NFS so symlinks can still be made to 
arbitrary locations.

Thanks...


-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst  |  henson at csupomona.edu
California State Polytechnic University  |  Pomona CA 91768