Hi, since my time is running out, I have now resorted to performing my install on the file system mounted with -o nodelalloc, and I am going to mount it this way in the running system, too, until I hear something about this issue being sorted. FWIW, I could reproduce the problem reliably three times on newly created file systems when mounted with delayed alloca- tion enabled, and it went away when I started using nodelalloc, so it does seem be in connection with this. Unfortunately I did not have the time to do runs with and without Ming's credit patch, however. But reading the code without truely understanding it, the non-da codepath calls the function to figure out the credits to reserver always with a single page argument, while the da case potentially hands it a larger number, and the resulting multiple then exceeds the maximum transaction size. As a closing note, it would be really cool if someone could put my mind at ease about being able to enable delayed allocation on the existing file system later after this is sorted, and about not missing out anything by not having it from the start. As I under- stand it right now, the only implications of not running with delalloc are little more fragmentation because the lack of the batching effect from delalloc results in missed chances to get contiguous blocks, and the FS will be slower without it, but otherwise, I'm not missing anything and can enable delalloc later, right? (Note: A nice answer might be eligible for the wiki, too - I'd gladly do the work to add it). Greetings, Peter -- 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
