arla 0.35.3 on FreeBSD 4.2-RELEASE gets confused about which volume it's in

[Love]

"Brandon S. Allbery KF8NH" <allbery at kf8nh.apk.net> writes:

> I've spent the past two days being frustrated by what appears to be
> confusion on the part of Arla.
> 
> I've been attempting to rebuild all of our Perl module collections to
> weed out conflicting files.  On FreeBSD this has resulted in strange
> behavior:
> 
> [getcwd problems]

These are all valid paths for this inode, the problems is that it changes.

> Suggestions on how to debug this?

It can be related to that we mark the node as not used in kernel before xfs
is done with it.

Is this bug repeatable ? Can you try this patch (against 0.35 branch) ?

Love

Index: arlad/messages.c
===================================================================
RCS file: /afs/stacken.kth.se/src/SourceRepository/arla/arlad/messages.c,v
retrieving revision 1.231.2.2
diff -u -w -u -w -r1.231.2.2 messages.c
--- messages.c	2001/02/11 06:13:07	1.231.2.2
+++ messages.c	2001/04/21 15:19:28
@@ -1816,9 +1816,11 @@
 
      assert (entry->flags.kernelp);
 
+#if 0
      entry->flags.kernelp   = FALSE;
      entry->flags.attrusedp = FALSE;
      entry->flags.datausedp = FALSE;
+#endif
 
      msg.header.opcode = XFS_MSG_INVALIDNODE;
      memcpy (&msg.handle, &entry->fid, sizeof(entry->fid));