From: Simon Gao <gao@schrodinger.com>
To: nfs@lists.sourceforge.net
Subject: Autofs failed auto umounting NFS shares exported by Solaris 10
Date: Mon, 23 Jul 2007 21:15:54 -0700 [thread overview]
Message-ID: <46A57CFA.2010507@schrodinger.com> (raw)
Hi,
I am seeing RHEL/CentOS 5.0 machine failed to un-mount NFS share
exported by Solaris 10 after time out period:
Here are errors logged:
Jul 23 20:14:45 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:19:48 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:24:51 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:29:54 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:34:57 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:40:00 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:45:03 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:50:06 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 20:55:09 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
Jul 23 21:00:12 client1 automount[1801]: umount_multi: could not stat fs
of /nfs/zfs
The autofs version is autofs-5.0.1-0.rc2.43.0.2.
Anyone has seen similar problem?
Simon
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2007-07-24 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 4:15 Simon Gao [this message]
2007-07-26 13:38 ` Autofs failed auto umounting NFS shares exported by Solaris 10 Ian Kent
2007-07-26 17:25 ` Simon Gao
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=46A57CFA.2010507@schrodinger.com \
--to=gao@schrodinger.com \
--cc=nfs@lists.sourceforge.net \
/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.