On Wed, Jul 2, 2014 at 12:03 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Wed, Jul 2, 2014 at 11:15 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
To totally avoid fragmentation, you have to assign the full space for each file at the instant of creation, and separate files one from another sufficiently so that they can grow. When the disk gets quite filled, the strategy fails. It is possible to move about files while the system is running, if designed carefully. The easiest is to move unused files on iddle system periods - but I don't know of any operating system doing it.
I'm not quite sure what you're saying. e4defrag will defrag an extent based filesystem (as opposed to a block based filesystem like ext2). It does it with the filesystem online.
Carlos, You may find it interesting that there is the beginnings of an effort to create e4defrag2. http://lists.openwall.net/linux-ext4/2014/04/28/3 I came across it because I saw this post where the same author is discussing some of his needs: http://markmail.org/message/vywin7l35krhq7vd If you google for IOC_MOV_DATA you will see someone has proposed a new ioctl that is similar to the one ext4 uses with e4defrag. I think that is good so that e4defrags underlying kernel code can get more use/testing. http://markmail.org/message/uypupmfcouasfeou Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org