On 08/12/2013 00:28, François Revol wrote: > On 07/12/2013 03:38, Ingo Weinhold wrote: >> If you also enable ktracing for syscalls, you'll be able to narrow it >> down easily to a single tracing item, so that you can get a stack trace. >> From there it should be straightforward to analyze the problem with more >> debug output. > > Well I spent some time digging how to use it but I didn't get a nice > tutorial (hey, could make a nice GCI task), so I only added some dprintf. > > The hints go down to BFS bfs_get_file_map() returning it (bfsinfo says > the file needs 9 block_runs, so obviously 8 vecs are not enough), called > from do_iterative_fd_io_iterate(). > > I reverted 24d0e21f51e88ab35cc3f1c1750741dfeb40933d > (do_iterative_fd_io_iterate(): Support sparse files) > ...locally and it reads the file just fine now. Ok I just removed the extra error == B_OK test in the for loop and it seems to work, but you really want to proofread it. François.