Florian Philipp <[email protected]> wrote: > > Even if the i-nodes are sequential on-disk, there's no reason to think > > that the data blocks associated with the inodes are in any particular > > order with respect to the i-nodes themselves. > > You could probably find the intended order by using debugfs (at least > for ext*). The following command should output the first physical block > of every file: > find /var/db/portage/ -type f -printf 'bmap <%i> 0\n' | sudo debugfs > /dev/mapper/vg-portage
This kind of order is not important for copy speed. Copy speed is dominated by write speed and write speed is dominated by seeks that are a result of keeping meta data up to date. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
