mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, Mateusz Guzik <mguzik@redhat.com>,
	Dave Chinner <david@fromorbit.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Josef Bacik <jbacik@fb.com>, Al Viro <viro@ZenIV.linux.org.uk>,
	Eric Sandeen <esandeen@redhat.com>
Subject: Re: [PATCH 2/2] fs: print a message when freezing/unfreezing filesystems
Date: Thu, 15 May 2014 15:46:10 +0200	[thread overview]
Message-ID: <20140515134610.GB660@quack.suse.cz> (raw)
In-Reply-To: <20140515124725.GA8194@thunk.org>

On Thu 15-05-14 08:47:25, Ted Tso wrote:
> On Thu, May 15, 2014 at 12:01:57PM +0200, Jan Kara wrote:
> >   I was tracking down a couple of times what the hell is freezing the
> > filesystem (and not unfreezing it) and I agree with Mateusz it would be
> > nice if we could tell after the fact who froze the fs. Maybe we could store
> > that information in superblock and dump it during emergency thaw?
> 
> Saving it in the superblock would require changing a bunch of file
> systems.  What if we store this information in memory, and print it
> out under certain conditions (i.e., after a soft lockup detection, or
> upon request of some magic sysrq request)?
  By 'superblock' I meant 'struct super_block' ;) So we are in agreement I
believe.

> Or we could create a tunable threshold and print a message after a
> file system has been frozen more than a particular specified duration,
> with that duration set conservatively to something like 60 or 120
> seconds by default.
  I was thinking about this as well but all these "warn after X seconds"
warnings tend to have quite a few false positives in practice so dumping
this in emergency-thaw sysrq handler or exposing the information somewhere
in proc (e.g. mountinfo) would look like a better option to me.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2014-05-15 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 18:31 [PATCH 1/2] fs: include device name in error messages about freezing Mateusz Guzik
2014-05-13 18:31 ` [PATCH 2/2] fs: print a message when freezing/unfreezing filesystems Mateusz Guzik
2014-05-13 18:39   ` Joe Perches
2014-05-13 18:53     ` Mateusz Guzik
2014-05-13 19:00       ` Joe Perches
2014-05-13 19:06         ` Mateusz Guzik
2014-05-14 21:54   ` Dave Chinner
2014-05-15  2:17     ` Theodore Ts'o
2014-05-15  3:04       ` Dave Chinner
2014-05-15  9:42     ` Mateusz Guzik
2014-05-15 10:01       ` Jan Kara
2014-05-15 10:43         ` Lukáš Czerner
2014-05-15 12:47         ` Theodore Ts'o
2014-05-15 13:46           ` Jan Kara [this message]
2014-05-15 14:15             ` Theodore Ts'o

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=20140515134610.GB660@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=david@fromorbit.com \
    --cc=esandeen@redhat.com \
    --cc=jbacik@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mguzik@redhat.com \
    --cc=tytso@mit.edu \
    --cc=viro@ZenIV.linux.org.uk \
    /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

all inboxes | Powered by JetHome®