You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by tastewar January 10, 2025
We have a snippet of code that is intended to process sparse holes in files with a loop like this:
std::vector<llfio::file_handle::extent_pair> ext = GetFileHandle().extents().value();
uint32_t startBlock = 0, endBlock = 0, oldEndBlock = 0;
for (auto it = ext.begin(); it != ext.end(); it++)
{
}
Seems to work fine on Linux, but in Windows, on a newly allocated 4096 byte file, we are getting back that there are 64 extents in the file. The first one looks correct, but the others all have 0xFFFFFFFF for both the beginning and length of the extent. Is this expected? Should we be ignoring any entries in the vector with 0xFFFFFFFF?
The text was updated successfully, but these errors were encountered:
Discussed in #154
Originally posted by tastewar January 10, 2025
We have a snippet of code that is intended to process sparse holes in files with a loop like this:
Seems to work fine on Linux, but in Windows, on a newly allocated 4096 byte file, we are getting back that there are 64 extents in the file. The first one looks correct, but the others all have 0xFFFFFFFF for both the beginning and length of the extent. Is this expected? Should we be ignoring any entries in the vector with 0xFFFFFFFF?
The text was updated successfully, but these errors were encountered: