[lkml]   [2019]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/1] udf: Fix incorrect final NOT_ALLOCATED (hole) extent length
Hi Jan,

On 6/4/19 7:31 AM, Steve Magnani wrote:

> In some cases, using the 'truncate' command to extend a UDF file results
> in a mismatch between the length of the file's extents (specifically, due
> to incorrect length of the final NOT_ALLOCATED extent) and the information
> (file) length. The discrepancy can prevent other operating systems
> (i.e., Windows 10) from opening the file.
> Two particular errors have been observed when extending a file:
> 1. The final extent is larger than it should be, having been rounded up
> to a multiple of the block size.
> B. The final extent is shorter than it should be, due to not having
> been updated when the file's information length was increased.

Wondering if you've seen this, or if something got lost in a spam folder.


Steven J. Magnani "I claim this network for MARS! Earthling, return my space modulator!"

#include <standard.disclaimer>

 \ /
  Last update: 2019-06-16 18:29    [W:0.117 / U:0.704 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site