From: Prashant Shah <pshah.mumbai@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: freeze_bdev hangs
Date: Fri, 12 Oct 2012 21:38:15 +0530 [thread overview]
Message-ID: <CAD6i1f+hqmjJAO1mAM3o2gtv4qMGJuosen28RLuAwMLMnFTYSw@mail.gmail.com> (raw)
In-Reply-To: <20121009214915.GD27882@quack.suse.cz>
Hi,
On Wed, Oct 10, 2012 at 3:19 AM, Jan Kara <jack@suse.cz> 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.
next prev parent reply other threads:[~2012-10-12 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 11:58 freeze_bdev hangs Prashant Shah
2012-10-05 17:33 ` Eric Sandeen
2012-10-08 7:43 ` Prashant Shah
2012-10-08 16:19 ` Jan Kara
2012-10-08 16:35 ` Prashant Shah
2012-10-09 21:49 ` Jan Kara
2012-10-12 16:08 ` Prashant Shah [this message]
2012-12-04 13:10 ` Prashant Shah
2012-10-08 18:21 ` Eric Sandeen
2012-10-08 18:48 ` Prashant Shah
2012-10-09 5:13 ` Prashant Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD6i1f+hqmjJAO1mAM3o2gtv4qMGJuosen28RLuAwMLMnFTYSw@mail.gmail.com \
--to=pshah.mumbai@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).