On Thu, Aug 5, 2010 at 10:26 PM, Andreas Dilger <andreas.dilger@xxxxxxxxxx> wrote: > > The current libext2fs and e2fsck code does not handle an internal journal inode size larger than 2GB because of 32-bit overflow. > I was surprised to see this problem description, since I have been using a 3GB journal with Next3 for a while and never observed this problem reported by fsck. Finally, I realized that the problem only happens when the journal inode size is larger than 4GB. Other than that, patch looks fine to me :-) Amir. -- 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
