Opened at 2007-07-14T05:45:05Z

Last modified at 2007-07-25T03:29:32Z

#88 closed defect

uploading a directory causes a brief dirnode exception — at Version 1

Reported by: warner Owned by: warner
Priority: minor Milestone: eventually
Component: code Version: 0.4.0
Keywords: dirnodes Cc:
Launchpad Bug:

Description (last modified by warner)

I'm not sure why, but uploading a directory (the tahoe source tree), using 'curl', causes a (benign) exception in the vdrive server: 

LOCAL:   File "/home/amduser/trunk/instdir/lib/allmydata/dirnode.py", line 81, in get
LOCAL:     raise KeyError("unable to find key %s" % idlib.b2a(key))
LOCAL: exceptions.KeyError: 'unable to find key uumzl6h4bokrkamr2z742hexgyg6oin2elowlkdrhfpd5hair3ya===='

I suspect that part of the upload process creates an empty directory and then tries to use it before the operation has completed, or something. I need to poke through the existing dirnodes and find which one references this one.

Change History (1)

comment:1 Changed at 2007-07-14T05:49:36Z by warner

  • Description modified (diff)
  • Status changed from new to assigned

the exception is marked as a LOCAL foolscap one, but the other three nodes don't have a corresponding REMOTE exception in their logs. It's possible that there's a fourth node out there that's connecting and trying to find its long-lost private dirnode, but the storage index keeps changing, and it seems to happen right at the beginning of a large directory upload.

Note: See TracTickets for help on using tickets.