The reason the donor file is created in the same directory as the source is to try and keep the block allocation policy consistent with the original inode. You may not need a SIGINT handler, since the timestamp could be reset as soon as the file is created and unlinked. It may also be possible to use O_TMPFILE on newer kernels to create the donor file to avoid any races? Cheers, Andreas > On Aug 15, 2014, at 22:45, TR Reardon <thomas_reardon@xxxxxxxxxxx> wrote: > > >>> On Fri, Aug 15, 2014 at 04:12:40PM -0400, TR Reardon wrote: >>> Currently, e4defrag creates a donor file _in the same directory_ of >>> the file being defrag'ed. >>> >>> The problem with this is that the containing directory times are >>> changed because of the transient presence of the donor file. Any >>> thoughts as to moving the donor to a better location, mount-root, or >>> /lost+found? Or, ugh, a configurable location, if non-privileged >>> defrag is important? >> >> How about we just reset the directory time? (Or does utime() not work?) >> >> --D > > Er, yes, that's simpler. And a SIGINT handler just to keep things tidy? > > +Reardon > > -- > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
