Follow-up Comment #2, bug #28779 (project hurd):
> So it is clear that ext2fs (or possibly libstore)
> has messed up encoding the blocks of the file, but I
> can't really tell what's wrong ATM. Possibly this
> could be a general bug in how ext2fs manages holes
> in files, so it should be further investigated.
It turns out the reason was pretty simple. When iterating
through the blocks of a file, diskfs_S_file_get_storage_info
counts down the number of allocated blocks, and not the
number of potential blocks.
This also explains Samuel's original observation that the
disk size matches the actual size of the file and not the
potential size.
This won't be a problem if we error out if the file contains
holes, which I'll be working on next.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?28779>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
