All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Smith <psmith@netezza.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: System hanging in /proc/mounts almost every night...	help!
Date: Wed, 04 Jun 2008 11:55:53 -0400	[thread overview]
Message-ID: <1212594953.7000.24.camel@psmithub.netezza.com> (raw)
In-Reply-To: <x49ve0picd3.fsf@segfault.boston.devel.redhat.com>

On Wed, 2008-06-04 at 09:00 -0400, Jeff Moyer wrote:
> This .Trash madness has to end.  It keep autofs from expiring mounts
> in other situations.  *grumble*

I'm looking into this and it absolutely does not make any sense, you're
right.  I've got a sample patch that will solve it that I'll propose to
the Gnome folks, but I think personally that my patch is just a quick
hack and something more comprehensive would be better (the types of
filesystems that are checked should be configurable, at least through
gconf or similar--my patch just hardcodes a check for "autofs").

Note this won't help the problem of non-expiring mounts: if you DO have
a .Trash file on the filesystem then, as you point out, this will keep
the partition mounted all the time.  Gross.

FYI, it happened again last night and again, the last thing in the log
was the .Trash thing.  However, I don't think that's the instigator per
se but rather a signpost.  It appears that whenever any filesystem is
mounted or unmounted, that silly .Trash search is triggered; apparently
the gvfsd-trash applet has an inotify or dbus or something set up to
find out when a mount or unmount happens.

I think it's the mount or (more likely) unmount that is both causing the
problem, AND triggering the .Trash search.

Anyway, I get those annoying .Trash messages many times a day but it
never seems to cause any problem.  But soon after I lock my system and
go home for the night, then it happens.  Last night I left about 7pm,
and the problem occurred at 9:43pm.


I'll set up the debugging you asked for, thanks.  Stay tuned for
tomorrow!

  reply	other threads:[~2008-06-04 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 19:39 System hanging in /proc/mounts almost every night... help! Paul Smith
2008-06-04 13:00 ` Jeff Moyer
2008-06-04 15:55   ` Paul Smith [this message]
2008-06-05 15:25   ` Paul Smith

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=1212594953.7000.24.camel@psmithub.netezza.com \
    --to=psmith@netezza.com \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.