Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compression > #668
| Path | csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news.stack.nl!.POSTED!not-for-mail |
|---|---|
| From | Willem <willem@toad.stack.nl> |
| Newsgroups | comp.compression |
| Subject | Re: PAR2 question |
| Date | Thu, 29 Dec 2011 18:35:38 +0000 (UTC) |
| Organization | Stack Usenet News Service |
| Lines | 30 |
| Message-ID | <slrnjfpcnq.1843.willem@toad.stack.nl> (permalink) |
| References | <fb5b85b9-daae-4a0e-b375-de8fa57be53a@q9g2000yqe.googlegroups.com> <slrnjffbm4.12ht.willem@turtle.stack.nl> <0310c174-d1a9-4994-9330-99d2c9867caa@l24g2000yqm.googlegroups.com> <2c9fb0db-e2ff-4f49-b6a4-8df502a76d77@t13g2000yqg.googlegroups.com> <1cde24f0-7bcf-4ec2-abbd-9514363b2d94@cs7g2000vbb.googlegroups.com> <28cd1a25-81ac-450d-970a-762ed3b9ab02@q9g2000yqe.googlegroups.com> |
| NNTP-Posting-Host | toad.stack.nl |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=us-ascii |
| Content-Transfer-Encoding | 7bit |
| X-Trace | mud.stack.nl 1325183738 31802 2001:610:1108:5010::135 (29 Dec 2011 18:35:38 GMT) |
| X-Complaints-To | abuse@stack.nl |
| NNTP-Posting-Date | Thu, 29 Dec 2011 18:35:38 +0000 (UTC) |
| User-Agent | slrn/0.9.9p1 (FreeBSD) |
| Xref | x330-a1.tempe.blueboxinc.net comp.compression:668 |
Show key headers only | View raw
Jim Leonard wrote:
) On Dec 27, 11:51?am, Industrial One <industrial_...@hotmail.com>
) wrote:
)> > You could "force" quickpar to "repair" the file if you lacked
)> > sufficient parity info, but there would be (in your above example) .1%
)> > bits incorrect all over the file. ?So what's worse: ?Knowing your file
)> > cannot be 100% repaired, or not knowing where in your file bits are
)> > incorrect?
)>
)> How do I do that? I don't see that option anywhere in Quickpar.
)
) By using quotes, I was implying a theoretical operation. You cannot
) actually force quickpar (or PAR2, which is what you should actually be
) using since it's not memory-constrained, slow, or broken like quickpar
) is) to just make up parity information.
I'm not sure that it's even theoretically possible to have quickpar/par2
partially repair a file. They use one CRC per block to identify the bad
blocks, and you need N 'good' blocks (of the N+M data+parity) to get the
original N data blocks back at all. So too much damage is just too much
damage.
SaSW, Willem
--
Disclaimer: I am in no way responsible for any of the statements
made in the above text. For all I know I might be
drugged or something..
No I'm not paranoid. You all think I'm paranoid, don't you !
#EOT
Back to comp.compression | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
PAR2 question Industrial One <industrial_one@hotmail.com> - 2011-12-25 13:25 -0800
Re: PAR2 question Willem <willem@turtle.stack.nl> - 2011-12-25 23:16 +0000
Re: PAR2 question Industrial One <industrial_one@hotmail.com> - 2011-12-26 08:33 -0800
Re: PAR2 question Jim Leonard <mobygamer@gmail.com> - 2011-12-27 09:20 -0800
Re: PAR2 question Industrial One <industrial_one@hotmail.com> - 2011-12-27 09:51 -0800
Re: PAR2 question Jim Leonard <mobygamer@gmail.com> - 2011-12-29 09:10 -0800
Re: PAR2 question Willem <willem@toad.stack.nl> - 2011-12-29 18:35 +0000
Re: PAR2 question "Captain Obvious" <udodenko@users.sourceforge.net> - 2011-12-31 18:26 +0200
csiph-web