Changes between Initial Version and Version 3 of Ticket #738


Ignore:
Timestamp:
2009-06-18T03:20:50Z (16 years ago)
Author:
warner
Comment:

(wrapped some of the description text to improve formatting)

I've looked a bit at the share file you sent me, and it seems ok (no corruption that I've seen so far). My next step is to examine the Incident report and see if I can figure out exactly which hash check failed, and compare them against hashes that I'll generate locally from that share.

Another approach will be to get a copy of two more shares, put them in a private grid, and attempt to download the file. If successful, the shares must be ok, and we'll focus on how the download process might be acting differently on your host.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #738

    • Property Component changed from unknown to code-encoding
    • Property Priority changed from major to critical
    • Property Keywords integrity added
    • Property Milestone changed from undecided to 1.5.0
    • Property Owner nobody deleted

  • Ticket #738 – Description

    initial v3  
    33Brief summary from flog debugger viewer:
    44
    5 <ValidatedReadBucketProxy #1>(2-<ReadBucketProxy 150097484 to peer [mgnbpxki] SI jow42sylefxjxsns3alv5ptghe>-m2st7xk76cvd): hash failure in block=0, shnum=2 on <ReadBucketProxy 150097484 to peer [mgnbpxki] SI jow42sylefxjxsns3alv5ptghe>
     5{{{
     6<ValidatedReadBucketProxy #1>
     7(2-<ReadBucketProxy 150097484 to peer [mgnbpxki] SI jow42sylefxjxsns3alv5ptghe>-m2st7xk76cvd):
     8 hash failure in block=0, shnum=2
     9 on <ReadBucketProxy 150097484 to peer [mgnbpxki] SI jow42sylefxjxsns3alv5ptghe>
    610
    711[...]
    … …  
    1216
    1317failure in block hash tree
     18}}}
    1419
    1520.. and so on.
    … …  
    1823
    1924tahoe get URI:CHK:lapry55oui4psmeiyxhvitfmpi:75mb37to6iauypych6bkqfkxxxfk6nhekhomzipkqzwt46v64hdq:3:5:99758080 meh
     25{{{
    2026Error, got 410 Gone
    21 NotEnoughSharesError: no shares could be found. Zero shares usually indicates a corrupt URI, or that no servers were connected, but it might also indicate severe corruption. You should perform a filecheck on this object to learn more.
     27NotEnoughSharesError: no shares could be found. Zero shares usually indicates
     28a corrupt URI, or that no servers were connected, but it might also indicate
     29severe corruption. You should perform a filecheck on this object to learn
     30more.
     31}}}
    2232
    2333Finally, dump-share on the 33MB file:
    2434
     35{{{
    2536share filename: /v/tahoe/.tahoe/storage/shares/jo/jow42sylefxjxsns3alv5ptghe/2
    2637             version: 1
    … …  
    4758
    4859 Lease #0: owner=0, expire in 2607324s (30 days)
     60}}}
    4961
    5062Machine details:
    5163
     64{{{
    5265NetBSD quickie 4.99.7 NetBSD 4.99.7 (quickie) #0: Tue Jan 2 14:47:23 PST 2007 root@quickie:/v/src/sys/arch/i386/compile/quickie i386
    5366
    … …  
    5568
    5669Python 2.5.2
     70}}}
    5771
    5872This is a transitional pthread machine, partway between the M:N -> 1:1 threading model transition. The M:N threads *should* be functional and for all system and most application purposes they are. (KDE, etc.) However, on occasion some software makes assumptions or is built without threading support because configure detected anomalous behaviour.