From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755847AbaEOWv6 (ORCPT ); Thu, 15 May 2014 18:51:58 -0400 Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:34841 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754031AbaEOWv5 (ORCPT ); Thu, 15 May 2014 18:51:57 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkkHAO5DdVN5LL1s/2dsb2JhbABZgwaDPqhfAQEBAQEBBpodAYESF3SCJQEBBTocIxAIAw4KCSUPBSUDIROIQNFXFxaFPoh6B4MrgRUEmVCTFYNIKw Date: Fri, 16 May 2014 08:51:41 +1000 From: Dave Chinner To: Mateusz Guzik Cc: =?utf-8?B?THVrw6HFoQ==?= Czerner , sandeen@redhat.com, Jan Kara , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Josef Bacik , Al Viro , Joe Perches Subject: Re: [PATCH V2 2/2] fs: print a message when freezing/unfreezing filesystems Message-ID: <20140515225141.GA26353@dastard> References: <20140514111449.GB5824@quack.suse.cz> <20140514112619.GA10637@mguzik.redhat.com> <20140514113945.GC5824@quack.suse.cz> <20140514220052.GD5421@dastard> <20140514223745.GF5421@dastard> <5373F0D6.4090600@redhat.com> <20140515104746.GF10637@mguzik.redhat.com> <20140515222135.GZ26353@dastard> <20140515223439.GA24089@mguzik.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140515223439.GA24089@mguzik.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 16, 2014 at 12:34:40AM +0200, Mateusz Guzik wrote: > On Fri, May 16, 2014 at 08:21:35AM +1000, Dave Chinner wrote: > > > IOW, a new column in mountinfo. For frozen filesystems it would contain > > > 'frozen_by=[%s]:[%d]' (escaped comm, pid). > > > > I really don't see that the process that froze the filesystem is > > particularly useful - it many cases that process is long gone (e.g. > > fsfreeze is being used to allow a HW array to take a snapshot). Just > > the fact it is in the process of freezing (if stuck, stack trace in > > sysrq-w should be present) or frozen (freezing process may be long > > gone, and is mostly irrelevant because you're now tracking down why > > a thaw hasn't happened)... > > There are deamons which perform freezing and unfreezing on their own. > Thus storing the name along with pid helps to determine whether someone > went behind such daemon's back, or maybe it's the daemon which "forgot" to > unfreeze after all. Such a daemon should be logging the fact that it's freezing and thawing the filesystem. The kernel is not the place to track what buggy userspace applications are doing wrong. Cheers, Dave. -- Dave Chinner david@fromorbit.com