Hi again, some more info: The x and y in the error messages used to be around 20k or 30k for x and 8192 for y. Googling around, it seems that's supposed to say that the maxium transaction size is 8192 blocks. Further, the maximum transaction size is supposedly 1/4 of the journal size. Assuming mke2fs -t ext4dev created the FS with 4096 blocks (dunno) that would mean the journal is 128MB, which is apparently typical. At least I have a 40GB ext3 here that got the same journal size. So I guess the question is why a basic operation like using links to download a 130MB tar archive to an ext4dev file sys- tem or unpacking it with tar would die by way of huge trans- actions that don't work with a normal journal. Still hoping I'll be able to continue with the installation today before the work week starts again ;). Kernel hackers read lists on Sunday, I hope :-). Greetings, Peter PS.: I'm writing via the shitty GMail web interface from an in- stall CD; here's hoping replying will work better than I fear it might. -- 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
