From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Philippe Troin <phil@fifi.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: silly-deleting symlinks?
Date: 01 Apr 2002 21:18:10 +0200 [thread overview]
Message-ID: <shsit7b6xe5.fsf@charged.uio.no> (raw)
In-Reply-To: <87hen5wrx4.fsf@ceramic.fifi.org>
>>>>> " " == Philippe Troin <phil@fifi.org> writes:
> I've just noticed that nfsd tries to silly-delete symlinks.
> Server: vanilla 2.2.20 SMP Client: vanilla 2.4.18 SMP Mount
> options: rw,nodev,v2,rsize=8192,wsize=8192,hard,intr,udp,lock
> Sometimes I see some .nfs<XXXX> files which are symlinks. How
> can symlinks be "in use" and be subject to silly-deletion?
Sillydelete just looks at the number of counts on the dentry. If the
count is > 1 then the dentry is deemed to be 'in use' no matter what
the type of inode.
Cheers,
Trond
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-04-01 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 21:56 silly-deleting symlinks? Philippe Troin
2002-04-01 19:18 ` Trond Myklebust [this message]
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=shsit7b6xe5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=phil@fifi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox