From: Chris Samuel <chris@csamuel.org>
To: Andreas Dilger <adilger@whamcloud.com>
Cc: Jan Kara <jack@suse.cz>, "J. Bruce Fields" <bfields@fieldses.org>,
ocfs2-devel@oss.oracle.com,
KONISHI Ryusuke <konishi.ryusuke@lab.ntt.co.jp>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-nilfs@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
cluster-devel@redhat.com, Anton Altaparmakov <anton@tuxera.com>,
linux-ext4@vger.kernel.org, fuse-devel@lists.sourceforge.net,
Mark Fasheh <mfasheh@suse.com>,
xfs@oss.sgi.com, Ben Myers <bpm@sgi.com>,
Joel Becker <jlbec@evilplan.org>,
dchinner@redhat.com, Steven Whitehouse <swhiteho@redhat.com>,
Chris Mason <chris.mason@oracle.com>,
linux-nfs@vger.kernel.org, Alex Elder <elder@kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
linux-ntfs-dev@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/19 v5] Fix filesystem freezing deadlocks
Date: Wed, 18 Apr 2012 10:46:55 +1000 [thread overview]
Message-ID: <4F8E0EFF.4090007@csamuel.org> (raw)
In-Reply-To: <141752A3-EDF1-4ABC-919D-4170B0455948@whamcloud.com>
On 17/04/12 15:10, Andreas Dilger wrote:
> (which IMHO would prevent nearly every Gnome system from freezing unless these
> apps have changed their behaviour in more recent releases).
It would also affect current KDE desktops as they tend to use MySQL for
Akonadi & Nepomuk, plus anyone using Chromium (and presumably Chrome):
samuel@eris:/tmp$ sudo lsof | grep deleted | awk '{print $1}' | sort |
uniq -c
[sudo] password for samuel:
32 chromium-
1 dovecot
5 imap-logi
5 mysqld
I would be surprised if you could find many systems that didn't have
files in this situation.
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-18 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 16:13 [PATCH 00/19 v5] Fix filesystem freezing deadlocks Jan Kara
2012-04-16 16:13 ` [PATCH 18/27] xfs: Convert to new freezing code Jan Kara
2012-04-16 16:16 ` [PATCH 00/19 v5] Fix filesystem freezing deadlocks Jan Kara
2012-04-16 22:02 ` Andreas Dilger
2012-04-17 0:43 ` Dave Chinner
2012-04-17 5:10 ` Andreas Dilger
2012-04-18 0:46 ` Chris Samuel [this message]
2012-04-17 9:32 ` Jan Kara
2012-04-17 19:34 ` Joel Becker
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=4F8E0EFF.4090007@csamuel.org \
--to=chris@csamuel.org \
--cc=adilger@whamcloud.com \
--cc=anton@tuxera.com \
--cc=bfields@fieldses.org \
--cc=bpm@sgi.com \
--cc=chris.mason@oracle.com \
--cc=cluster-devel@redhat.com \
--cc=davem@davemloft.net \
--cc=dchinner@redhat.com \
--cc=elder@kernel.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=jlbec@evilplan.org \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=mfasheh@suse.com \
--cc=miklos@szeredi.hu \
--cc=ocfs2-devel@oss.oracle.com \
--cc=swhiteho@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
--cc=xfs@oss.sgi.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