[tahoe-dev] [tahoe-lafs] #970: Tahoe Put can cause directory corruption

tahoe-lafs trac at allmydata.org
Tue Feb 23 05:28:21 UTC 2010

#970: Tahoe Put can cause directory corruption
 Reporter:  stott     |           Owner:  nobody   
     Type:  defect    |          Status:  new      
 Priority:  critical  |       Milestone:  undecided
Component:  unknown   |         Version:  1.5.0    
 Keywords:            |   Launchpad_bug:           
 Multiple simultaneous Tahoe put(s) via web API cause directory level
 corruption resulting in no recoverable data.

 To recreate

 Step 1.) Create Directory ; Get directory writecap.

 Step 2.) Using 61 .JPG files avg 1.7MB  use test.sh script to put files to

 bash-3.2$ du -sh .
 bash-3.2$ ls *.JPG |wc -l
 bash-3.2$ cat test.sh

 # From Directory listing itself == Directory Write CAP

 for I in `ls *.JPG`
 curl -T $I$X/uri/$FW/$I &
 #echo "curl -T $I$X/uri/$FW/$I & "
          X=`expr $X + 1`
         if [ $X -le 3500 ] ; then
            echo "Submitting $I"
            else X=3456;


 Error returned from curl

 UnrecoverableFileError: the directory (or mutable file) could not be
 retrieved, because there were insufficient good shares. This might
 indicate that no servers were connected, insufficient servers were
 connected, the URI was corrupt, or that shares have been lost due to
 server departure, hard drive failure, or disk corruption. You should
 perform a filecheck on this object to learn more.


 Error Generated when trying to retrieve known good URI from child



Ticket URL: <http://allmydata.org/trac/tahoe/ticket/970>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid

More information about the tahoe-dev mailing list