From: Eric Sandeen <sandeen@redhat.com>
To: Prashant Shah <pshah.mumbai@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: freeze_bdev hangs
Date: Mon, 08 Oct 2012 13:21:36 -0500 [thread overview]
Message-ID: <507319B0.8040202@redhat.com> (raw)
In-Reply-To: <CAD6i1fJbfiBnTu1ttisMr96PzaTWCLAsvmTjx7OevfPcAGd7-A@mail.gmail.com>
On 10/8/12 2:43 AM, Prashant Shah wrote:
> Hi,
>
> On Fri, Oct 5, 2012 at 11:03 PM, Eric Sandeen <sandeen@redhat.com> wrote:
>> I haven't looked at your custom code, but freeze has changed a bit lately,
>> and "hangs" is a very vague description
>>
>> -Eric
>
> I am monitoring the file system (ext3) for block writes and on
> linux-2.6.18 (centos - 5.8 64bit) there are lots of writes request per
> second with inode number set to 0 even when the file system is idle
> and without any work loads. Didnt see this happen on linux-3.x.
>
> filter: sector=242983 inode=0
if you dumpe2fs your fs you may find those sectors contain metadata not data.
Anyway, did you try the suggestions I offered to track down your original
question about the freeze deadlock?
-Eric
> filter: sector=242991 inode=0
> filter: sector=242999 inode=0
> filter: sector=243007 inode=0
> filter: sector=243015 inode=0
> filter: sector=243023 inode=0
> filter: sector=243031 inode=0
> filter: sector=243039 inode=0
>
> What are these request with inode number as 0 ? All the special inode
> numbers start from 1.
>
> http://lxr.linux.no/#linux+v2.6.32/include/linux/ext3_fs.h#L56
>
> Regards.
>
next prev parent reply other threads:[~2012-10-08 18:21 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
2012-12-04 13:10 ` Prashant Shah
2012-10-08 18:21 ` Eric Sandeen [this message]
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=507319B0.8040202@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pshah.mumbai@gmail.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).