Bernd Schubert wrote: ... > Altogether filesystem unrelated. The filesystem just might be the reason for a > synchronize-cache, e.g. barriers, etc. Interesting that it only happens at enospc time though - the fs would be sending barriers in general usage. Although, as ext4 fills, it does do more syncing/flushing to try to eke out that last bit of space.... hmm.... Andre, just for fun, you might try mounting -o nodelalloc, fill it again, and see if you see the same behavior. If not, you might do it again w/ defaults, and capture blktrace data, which I think will trace barrier requests as well. (or, maybe also try testing with -o nobarrier) I still don't think it's likely a filesystem problem but maybe you can pinpoint the fs behavior that triggers it. -Eric > Greetings from Tübingen, > Bernd > -- > 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
