> Thanks, that's really helpful. I can say that using a 4MB journal and > running fsstress is _not_ enough to trigger the problem. > > Looking more closely at what might be needed to trigger the bug, 'i' > gets left uninitialized when err is set to -EAGAIN, and that happens > when ext4_ext_truncate_extend_restart() is unable to extend the > journal transaction. But that also means we need to be deleting a > sufficiently large enough file that the blocks span multiple block > groups (which is why we need to extend the transaction, so we can > modify more bitmap blocks) at the point when there is no more room in > the journal, so we have to close the current transaction, and then > retry it again with a new journal handle in a new transaction. > > So that implies that untaring a bunch of kernels probably won't be > sufficient, since the files will be too small. What we probably will > need to do is to fill a large file system with lots of large files, > use a small journal, and then try to do an rm -rf. > > - Ted My suggestion of untarring kernels was to cause the big multi gigabyte files created later on to be massively fragmented, and thus have tons of extents and a relatively deep extent tree. But maybe that's not needed to trigger this bug, if as you say, it is caused by the absolute number of disks blocks being freed and not by the size/depth/complexity of the extent tree. My knowledge of the internals of ext4 is pretty much non-existent. ;-) In this case I'm just an end user. -- 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
