par2repair

[milomak]

i've noticed something new in my par2repair.

i'll run it. it will fix the affected files. i'll run it again. it will say no repair needed. i'll run it again and suddenly there are files to repair again.

and the files are different from the first batch that was repaired.

this is on debian. anyone experiencing similar on other par2repairs?

 

[MyWorld]

I have not needed par2repair or quite some time now, will check when next time I need to use it.

 

[psheldon]

That started quite awhile back, I use Quickpar/windoze and wine I unfortunately do have XP available.

 

[louisvd]

I haven't noticed that on Fedora 14 - but then once repaired I usually extract the files, and don't re-run par2.

What I *AM* having problems with it why e.g. parfile.15+16, so some such filename, can't repair a 31 block missing set of files. Surely that naming convention means it has 15 existing plus another extra 16 blocks? Lately I get a number threads that seem to miss *just* one too many to be able to repair. Very frustrating!

 

[qinglung]

What I *AM* having problems with it why e.g. parfile.15+16, so some such filename, can't repair a 31 block missing set of files. Surely that naming convention means it has 15 existing plus another extra 16 blocks?

In the naming convention, the last digit shows the number of blocks in the current PAR file, so parfile.15+16 only has 16 blocks. The 15 indicates the number of blocks available if you download all the previous PAR files in the set. Normally the previous ones will contain 1, 2, 4 and 8 blocks respectively, giving you 15 in total.

 

[milomak]

i suspect it was an isp issue at the time.