From: Mateusz Guzik <mguzik@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: "Lukáš Czerner" <lczerner@redhat.com>,
sandeen@redhat.com, "Jan Kara" <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Josef Bacik" <jbacik@fb.com>,
"Al Viro" <viro@ZenIV.linux.org.uk>,
"Joe Perches" <joe@perches.com>
Subject: Re: [PATCH V2 2/2] fs: print a message when freezing/unfreezing filesystems
Date: Fri, 16 May 2014 02:39:27 +0200 [thread overview]
Message-ID: <20140516003926.GC24089@mguzik.redhat.com> (raw)
In-Reply-To: <20140516001156.GI5421@dastard>
On Fri, May 16, 2014 at 10:11:56AM +1000, Dave Chinner wrote:
> On Fri, May 16, 2014 at 01:19:09AM +0200, Mateusz Guzik wrote:
> > Except there is no log entry if /var got frozen (and this is not an
> > imaginary example).
>
> Freezing the filesystem that the freezing daemon logs to is, well, a
> major application architecture fail. Sorry, catering for the lowest
> common denominator (i.e. stupidity) is not an valid argument for
> adding stuff to the kernel....
>
I'm only saying what you can encounter in varous companies. If aiding this
problem the way I proposed is not a good idea (and it turns out there is
a much better way), I'm not insisting.
> > Grabbig a debugger to inspect daemon's state is not
> > exactly what your typical support associate can or should do.
>
> No, but they can read /proc/self/mountinfo, and grab sysrq-w output.
> And they should be able to read that and tell that there is a freeze
> hang from that info. This "filesystem hang triage 101" stuff....
>
> > But this was a side request, I'm not going to argue about including
> > this since turns out there is a better way.
> >
> > Somewhere in the thread an idea to log long-standing freezes was
> > mentioned which would provide sufficient information as far as
>
> You've already got the hung task timer firing when a fs is frozen
> for too long. You'll see processes hung in sb_write_wait(), and that
> tells you the filesystem is frozen. Then look at
> /proc/self/mountinfo to find which fs is frozen....
>
But additional question was what initiated the freeze and it is not
answered by this. Hopefully a warning for long-standing freezes will be
implemented and that will answer the question.
Once more, I'm fine with mere 'frozen' in mountinfo, so I suggest we
drop this now side subject. If you really want to continue we can
discuss this in private. :->
--
Mateusz Guzik
next prev parent reply other threads:[~2014-05-16 0:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 22:04 [PATCH V2 1/2] fs: include device name in error messages about freezing Mateusz Guzik
2014-05-13 22:04 ` [PATCH V2 2/2] fs: print a message when freezing/unfreezing filesystems Mateusz Guzik
2014-05-14 11:14 ` Jan Kara
2014-05-14 11:26 ` Mateusz Guzik
2014-05-14 11:39 ` Jan Kara
2014-05-14 22:00 ` Dave Chinner
2014-05-14 22:37 ` Dave Chinner
2014-05-14 22:40 ` Eric Sandeen
2014-05-15 10:40 ` Lukáš Czerner
2014-05-15 10:47 ` Mateusz Guzik
2014-05-15 22:21 ` Dave Chinner
2014-05-15 22:34 ` Mateusz Guzik
2014-05-15 22:51 ` Dave Chinner
2014-05-15 23:19 ` Mateusz Guzik
2014-05-16 0:11 ` Dave Chinner
2014-05-16 0:39 ` Mateusz Guzik [this message]
2014-05-19 9:43 ` Jan Kara
2014-05-19 23:37 ` Dave Chinner
2014-05-15 10:13 ` Jan Kara
2014-05-15 22:16 ` Dave Chinner
2014-05-14 11:58 ` Lukáš Czerner
2014-05-14 11:10 ` [PATCH V2 1/2] fs: include device name in error messages about freezing Jan Kara
2014-05-14 22:07 ` Dave Chinner
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=20140516003926.GC24089@mguzik.redhat.com \
--to=mguzik@redhat.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=joe@perches.com \
--cc=lczerner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).