From: Prashant Shah Subject: Re: freeze_bdev hangs Date: Tue, 9 Oct 2012 00:18:15 +0530 Message-ID: References: <506F19E6.8030005@redhat.com> <507319B0.8040202@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-ext4@vger.kernel.org To: Eric Sandeen Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:36736 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753480Ab2JHSsh (ORCPT ); Mon, 8 Oct 2012 14:48:37 -0400 Received: by mail-ee0-f46.google.com with SMTP id b15so2995958eek.19 for ; Mon, 08 Oct 2012 11:48:36 -0700 (PDT) In-Reply-To: <507319B0.8040202@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: Hi, On Mon, Oct 8, 2012 at 11:51 PM, Eric Sandeen wrote: > > if you dumpe2fs your fs you may find those sectors contain metadata not data. Why is inode number 0 even if its journal or meta data ? Also I am getting *lots* of write per second on a bare metal centos with nothing running. Its strange. Didn't see it on 3.x. > Anyway, did you try the suggestions I offered to track down your original > question about the freeze deadlock? I am not facing any deadlocks on 2.6.18 but was facing it on 3.x. freeze_bdev() and thaw_bdev() work correctly on 2.6.18. I will try it again on 3.x and confirm. Regards.