On 26 March 2012 23:08, David Korn <[email protected]> wrote: > cc: [email protected] > Subject: Re: Re: [ast-users] Implementing SEEK_HOLE, SEEK_DATA in AST cp, mv, > pax > -------- > > >> Well, it does something but IMO not the correct thing, where 'correct' >> is defined as now FreeBSD, Solaris, GNU coreutils/Linux etc do it. The >> cp, mv, pax commands should preserve the exact location of holes in a >> sparse files if src and dest are on the same filesystem which is what >> the majority of implementations of these commands now do. >> >> > > No, the AST write operation always tries to shrink the file by creating > holes as much as possible. Since holes are transparent to applications, > other than using additional space, why does it matter whether there are > holes are not?
If an application can differ between holes and areas with data it can use this information for it's advantage. However if an application depends on holes and their precise layout in a file then destroying this layout will lead to a dataloss situation. _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
