[tahoe-lafs-trac-stream] [tahoe-lafs] #970: webapi PUT via multiple nodes can cause directory corruption but does not report UncoordinatedWriteError
tahoe-lafs
trac at tahoe-lafs.org
Tue Aug 16 17:14:27 PDT 2011
#970: webapi PUT via multiple nodes can cause directory corruption but does not
report UncoordinatedWriteError
-----------------------------------+---------------------------------------
Reporter: stott | Owner: nobody
Type: defect | Status: new
Priority: minor | Milestone: undecided
Component: code-frontend-web | Version: 1.5.0
Resolution: | Keywords: error usability ucwe docs
Launchpad Bug: |
-----------------------------------+---------------------------------------
Description changed by davidsarah:
Old description:
> 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 Tahoe-Lafs.
>
> -------------------
> bash-3.2$ du -sh .
> 102m
> -------------------
> bash-3.2$ ls *.JPG |wc -l
> 61
> -------------------
> {{{
> bash-3.2$ cat test.sh
> #!/bin/sh
>
> # From Directory listing itself == Directory Write CAP
> FW="URI:DIR2:tuz27wvy27ua4mt5lyotllbyke:phzv6ilb5gssi3zy33nki62zcudqjzyv7v7w4qaavwn5kuh2hawa"
>
>
> X=3456
> for I in `ls *.JPG`
> do
> curl -T $I http://10.20.0.151:$X/uri/$FW/$I &
> #echo "curl -T $I http://10.20.0.151:$X/uri/$FW/$I & "
> X=`expr $X + 1`
> if [ $X -le 3500 ] ; then
> echo "Submitting $I"
> else X=3456;
> fi
> done
> }}}
> -------------------------------------------
>
> 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
>
> http://codepad.org/mTFYmfxf
>
> -------------------------
New description:
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
Tahoe-Lafs.
-------------------
bash-3.2$ du -sh .
102m
-------------------
bash-3.2$ ls *.JPG |wc -l
61
-------------------
{{{
bash-3.2$ cat test.sh
#!/bin/sh
# From Directory listing itself == Directory Write CAP
FW="URI:DIR2:tuz27wvy27ua4mt5lyotllbyke:phzv6ilb5gssi3zy33nki62zcudqjzyv7v7w4qaavwn5kuh2hawa"
X=3456
for I in `ls *.JPG`
do
curl -T $I http://10.20.0.151:$X/uri/$FW/$I &
#echo "curl -T $I http://10.20.0.151:$X/uri/$FW/$I & "
X=`expr $X + 1`
if [ $X -le 3500 ] ; then
echo "Submitting $I"
else X=3456;
fi
done
}}}
-------------------------------------------
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:
[attachment:970-paste.txt]
-------------------------
--
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/970#comment:8>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list