Hi, On Wed, Oct 10, 2012 at 3:19 AM, Jan Kara <jack@xxxxxxx> wrote: > OK. There are several ways how I could imagine you hit ino == 0. Either > someone is using direct IO or inode is a block device inode... > Fixed one of the issues. It turn out that printk() in the request function cause the /var/log/messages file to be updated that resulted in more block copies in request function which in turn triggered more printk's. I will check the direct IO operations and report back. Regards. -- 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
