Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
md5 for test08 on 128k disk?
1 view
Skip to first unread message
Adrian Kubala
May 10, 2005, 1:41:24 AM5/10/05
to
Is there any chance we could see the md5 or disk contents for test08 on
a 128k disk? Having verified that my implementation is writing the
correct filesize and filling up to the very last block, I'm not sure
what else I can check to ensure that it passes the test. I'm wondering
if there's some subtle difference in the way the reference
implementation calls getAppData in this case.
a 128k disk? Having verified that my implementation is writing the
correct filesize and filling up to the very last block, I'm not sure
what else I can check to ensure that it passes the test. I'm wondering
if there's some subtle difference in the way the reference
implementation calls getAppData in this case.
Yiu Fai Sit
May 10, 2005, 2:56:55 AM5/10/05
to
If you call getAppData for each block, using the length to be written in
each block, then there should be no problem.
Sit
Adrian Kubala
May 10, 2005, 12:01:10 PM5/10/05
to
Yiu Fai Sit <yf...@cs.utexas.edu> schrieb:
I did find one problem: when I try and fail to allocate a block, I was
neglecting to unallocate the extra block I allocated. Although this
doesn't seem to affect the DiskDumper contents.
Jon Lemon
May 10, 2005, 12:08:26 PM5/10/05
to
that difference of a block will only show up in your used block bitmap
(ie, the overall md5sum), which diskdumper does not look at.
(ie, the overall md5sum), which diskdumper does not look at.
Yiu Fai Sit
May 10, 2005, 12:55:03 PM5/10/05
to
but don't leave it unfixed. If you were to write a bunch of these files,
you will get disk full much earlier.
you will get disk full much earlier.
Sit
0 new messages