From: Ondrej Valousek <webserv@s3group.cz>
To: Ian Kent <raven@themaw.net>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: expire_indirect errors in the syslog
Date: Thu, 06 Nov 2008 13:22:39 +0100 [thread overview]
Message-ID: <4912E18F.7010701@s3group.cz> (raw)
In-Reply-To: <1225192753.2938.103.camel@zeus.themaw.net>
Ok, I have removed all "nohide" options from my exports, but I am still
experiencing the expire_indirect errors.
I must also say that I am also using NetApp NAS and one share is nfs4
mounted.
But I do not believe it is NetApp/nfs4 related.
Question:
Is it possible that I receive this errors when:
1. say I have autofs key like "share nfsserver:/exports/share"
2. some processes start using the share
3. I delete the key above and delete the share from the NFS server
4. As the share no longer exists but some processes are still using it,
automounter can not unmount it, so I manually invoke umount -l to remove it.
Thanks,
Ondrej
next prev parent reply other threads:[~2008-11-06 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 7:46 expire_indirect errors in the syslog Ondrej Valousek
2008-10-28 8:04 ` Ian Kent
2008-10-28 8:19 ` Ondrej Valousek
2008-10-28 11:19 ` Ian Kent
2008-11-06 12:22 ` Ondrej Valousek [this message]
2008-11-07 1:20 ` Ian Kent
2008-11-07 7:42 ` Ondrej Valousek
2008-11-07 8:47 ` Ian Kent
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=4912E18F.7010701@s3group.cz \
--to=webserv@s3group.cz \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.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.