All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Weber <jweber@amsuper.com>
To: autofs@linux.kernel.org
Subject: unmount immediately followed by remount
Date: Fri, 8 Jun 2007 14:29:02 -0500	[thread overview]
Message-ID: <200706081429.02284.jweber@amsuper.com> (raw)

I have 2 WinXP servers, I am automounting using smbs.  For one server, the 
automounter unmounts the smbfs after inactivity as expected.  For the other 
server, supermad2, the automounter expires and unmounts the 4 shares after 
approx the 60sec timeout, as expected.  However, the shares are then 
immediately remounted.  Thus, the shares from the server are effectively 
continuously mounted.  Here's some sample automount debug output:

Jun  8 14:09:36 quetzal automount[31118]: handle_packet: type = 2
Jun  8 14:09:36 quetzal automount[31118]: handle_packet_expire_multi: token 
297,
 name supermad2
Jun  8 14:09:36 quetzal automount[31651]: expiring path /smb/supermad2
Jun  8 14:09:36 quetzal automount[31651]: umount_multi: path=/smb/supermad2 
incl
=1
Jun  8 14:09:36 quetzal automount[31651]: umount_multi: unmounting 
dir=/smb/supermad2/TRANSFER
Jun  8 14:09:36 quetzal automount[31651]: umount_multi: unmounting 
dir=/smb/supermad2/MDUsers
Jun  8 14:09:36 quetzal automount[31651]: umount_multi: unmounting 
dir=/smb/supermad2/CAD
Jun  8 14:09:36 quetzal automount[31651]: umount_multi: unmounting 
dir=/smb/supermad2/ENG
Jun  8 14:09:36 quetzal automount[31651]: rm_unwanted: /smb/supermad2/TRANSFER
Jun  8 14:09:36 quetzal automount[31651]: rm_unwanted: /smb/supermad2/MDUsers
Jun  8 14:09:36 quetzal automount[31651]: rm_unwanted: /smb/supermad2/ENG
Jun  8 14:09:36 quetzal automount[31651]: rm_unwanted: /smb/supermad2/CAD
Jun  8 14:09:36 quetzal automount[31651]: expired /smb/supermad2
Jun  8 14:09:36 quetzal automount[31118]: handle_child: got pid 31651, sig 0 
(0)
, stat 0
Jun  8 14:09:36 quetzal automount[31118]: sig_child: found pending iop pid 
31651
: signalled 0 (sig 0), exit status 0
Jun  8 14:09:36 quetzal automount[31118]: send_ready: token=297
Jun  8 14:09:36 quetzal automount[31118]: handle_packet: type = 0
Jun  8 14:09:36 quetzal automount[31118]: handle_packet_missing: token 298, 
name
 supermad2
Jun  8 14:09:36 quetzal automount[31118]: attempting to mount 
entry /smb/supermad2

lsof and fuser show the mounted filesystems are not busy.  I would think if 
the filesystems were busy, they would not be unmounted.  I can't imagine why 
the automounter would cycle with mount, unmount, mount, ...
with effectively zero unmounted time.

my config:
SuSE 10.1
Linux kernel 2.6.16.27-0.9-default
Linux automount version 4.1.4

	thanks,
	Jeff
-- 
Jeff Weber
American Superconductor Corp.

             reply	other threads:[~2007-06-08 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 19:29 Jeff Weber [this message]
2007-06-08 20:10 ` unmount immediately followed by remount Jeff Moyer

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=200706081429.02284.jweber@amsuper.com \
    --to=jweber@amsuper.com \
    --cc=autofs@linux.kernel.org \
    /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.