AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070823232555.70c966a8@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<jonathan.goldick@onstor.com>,<jobi.ariyamannil@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E019AF86F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Thu, 23 Aug 2007 23:26:09 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>
Cc: "Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>
Subject: Re: can't remove directory heirarchy
Message-ID: <20070823232609.6c091a09@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E019AF86F@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E019AF86F@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Wow, I'm trying to wrap my walnut sized brain around this.  So the
client is using the .nfs files as record keeping turds to know to hide
"deleted" files from the client[s] even though they haven't really been
deleted from the server yet because they are open.  What was weirding me
out was that I couldn't delete the directories.  But I guess the upshot
is that the .nfs files themselves were keeping the directories from
being deleted.  Even though that's basically breaking the paradigm,
there's not a lot the client can do because of the NFS semantics.  The
files themselves were "gone" as far as my client threads were
concerned, including the vim processes, which were reporting the files
as "...no longer available."  Very strange.  Kind of cool though. In a
freak-ass, god-I'm-a-geek, sort of way.

a

On Thu, 23 Aug 2007 23:03:50 -0700 "Jonathan Goldick"
<jonathan.goldick@onstor.com> wrote:

> I believe that these files are locked only on the nfs client.  Any
> other nfs client could delete them.  This is how nfs clients protect
> open files.
> 
> 
> 
> -----Original Message-----
> From: Andy Sharp
> To: Jobi Ariyamannil
> CC: Jonathan Goldick
> Sent: Thu Aug 23 22:43:14 2007
> Subject: can't remove directory heirarchy
> 
> Hi Jobi,
> 
> Check this out: I'm trying to remove a directory heirarchy, and all
> the files were deleted, except a couple of .nfs.... files, and I can't
> delete them and therefore I can't delete the directories.  Kind of
> weird.
> 
> 
> ripper:~/src/dev/linux/Pkgs/source/kexec-tools$ rm -rf
> kexec-tools-1.101-kdump10/ rm: cannot remove
> `kexec-tools-1.101-kdump10//debian/patches/.nfs000000000160361400000009':
> Device or resource busy rm: cannot remove
> `kexec-tools-1.101-kdump10//debian/patched/.nfs00000000015fb3010000000a':
> Device or resource busy
> 
> 
> It seems to be because I have a couple of vi sessions going,
> ostensibly on files in that heirarchy, but I should still be able to
> delete the whole thing.  Is this a client bug?  Or a filer bug?
