[tahoe-dev] Help uploading when file exists but needs repair

[Kyle Markley]

 Brian, David-Sarah,

> So, next steps:
>  1: confirm we're looking at the right file

 Confirmed.  Nice to know how to do this, now!

>  2: get a flog trace of the failing upload

 Here's the dump output (it's short!), and the flog.out.gz is attached 
 to this message.

 xxaj2tgm#678 20:43:48.719: CHKUploader starting
 xxaj2tgm#679 20:43:48.719: starting upload of 
 <allmydata.immutable.upload.EncryptAnUploadable instance at 0x209d3b488>
 xxaj2tgm#680 20:43:48.719: creating Encoder <Encoder for unknown 
 storage index>
 xxaj2tgm#681 20:43:48.719: file size: 398
 xxaj2tgm#682 20:43:48.719: my encoding parameters: (2, 4, 4, 398)
 xxaj2tgm#683 20:43:48.719: got encoding parameters: 2/4/4 398
 xxaj2tgm#684 20:43:48.719: now setting up codec
 xxaj2tgm#685 20:43:48.719: using storage index dumi2
 xxaj2tgm#686 20:43:48.719: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): starting
 xxaj2tgm#687 20:43:48.732: storage: allocate_buckets 
 dumi26otgmnemrypt3zlesxm5y
 xxaj2tgm#688 20:43:48.735: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): response to allocate_buckets() from peer xxaj2tgm: 
 alreadygot=(), allocated=(0,)
 xxaj2tgm#689 20:43:48.758: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): response to allocate_buckets() from peer juwmgssm: 
 alreadygot=(0, 3), allocated=(1,)
 xxaj2tgm#690 20:43:48.821: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): response to allocate_buckets() from peer vjqcroal: 
 alreadygot=(1,), allocated=(2,)
 xxaj2tgm#691 20:43:48.824: storage: aborting sharefile 
 /storage/_tahoe/.tahoe/storage/shares/incoming/du/dumi26otgmnemrypt3zlesxm5y/0
 xxaj2tgm#692 20:43:48.882: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): response to allocate_buckets() from peer 47cslusc: 
 alreadygot=(), allocated=(0,)
 xxaj2tgm#693 20:43:48.882: <Tahoe2PeerSelector for upload 
 dumi2>(dumi2): server selection unsuccessful for <Tahoe2PeerSelector for 
 upload dumi2>: shares could be placed on only 3 server(s) such that any 
 2 of them have enough shares to recover the file, but we were asked to 
 place shares on at least 4 such servers. (placed all 4 shares, want to 
 place shares on at least 4 servers such that any 2 of them have enough 
 shares to recover the file, sent 4 queries to 4 peers, 4 queries placed 
 some shares, 0 placed none (of which 0 placed none due to the server 
 being full and 0 placed none due to an error)), merged=sh0: 47cslusc, 
 sh1: vjqcroal+juwmgssm, sh2: vjqcroal, sh3: juwmgssm
 xxaj2tgm#694 20:43:48.886: web: 127.0.0.1 PUT /uri/[CENSORED].. 500 
 1610


>  3: get David-Sarah or somebody who understands the current
>     share-placement to take a look

 Have fun, guys.  :)  I'll be happiest if this maps to one of the known 
 failure cases!

-- 
 Kyle Markley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: flog.out.gz
Type: application/gzip
Size: 1814 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20101201/efbe3ff4/attachment.bin>