From: Jan Kara Subject: Re: freeze_bdev hangs Date: Tue, 9 Oct 2012 23:49:15 +0200 Message-ID: <20121009214915.GD27882@quack.suse.cz> References: <506F19E6.8030005@redhat.com> <20121008161926.GH9243@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kara , Eric Sandeen , linux-ext4@vger.kernel.org To: Prashant Shah Return-path: Received: from cantor2.suse.de ([195.135.220.15]:35533 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757050Ab2JIVtR (ORCPT ); Tue, 9 Oct 2012 17:49:17 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Mon 08-10-12 22:05:38, Prashant Shah wrote: > Hi, > > On Mon, Oct 8, 2012 at 9:49 PM, Jan Kara wrote: > > And what tool are you using for monitoring? > > I am using printk(). A custom module that changes the make_request_fn > of the block device to a custom callback. In the callback I am > printing the request bio details and passing the bio back to the > original make_request_fn. 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... Honza