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? I don't understand what happens if you copy a file across file systems with different block sizes and/or on systems that don't support holes. With the sfio copy, it will create holes if possible. it leaves it up to the file systems by doing an lseek to the offset of the next non-zero byte after encountering some number of 0 bytes. David Korn [email protected] _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
