2011/06/16 17:18, Tomasz Chmielewski wrote:
I noticed that when using e4defrag on such a file-based image, while the guest is running (i.e. the file is in use), all IO from that guest to the disk (disk is this file) is "frozen". In other words, as soon as we run e4defrag, any guest writes to that file will only complete if e4defrag finishes. As the images can be quite big, it can mean guest IO can be frozen even for hours. Is it a known/intended limitation (at least, it behaved like this when I tried e4defrag a few months ago)?
Thank you for the feedback. I will try to reproduce this problem later. Regards, Kazuya Mio -- 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
