Re: "dpkg --info" produces errors if /tmp NFS mounted
Brian May (bam@snoopy.apana.org.au)
Wed, 10 Mar 1999 18:25:27 +1100
Trond Myklebust wrote:
>Brian May <bam@snoopy.apana.org.au> writes:
>
>>
>> dpkg --info /home/ftp/files/linux/hurd-i386/base/timezones_2.0.110-0.1.deb
>> [... good output deleted...]
>> rm: /tmp/00545aaa/.nfs58031b3b00000013: Device or resource busy
>> rm: /tmp/00545aaa: Device or resource busy
>> rm cleanup failed, code 256
>
>In NFS you cannot delete a file that another process is holding open
>as this would cause the file to physically disappear. The standard
>trick (on all UNIX NFS clients) is to rename the open file to some
>unique and very unlikely name (typically .nfsxxxxx), and then to
>postpone deleting it until it is closed. Since deleting such a file
>makes no sense, it is not allowed.
I realize that, I want to do what I should do to fix the problem.
dpkg shouldn't generate the error message. First I have to
know if the problem is the kernel or dpkg...
IMHO, it is the kernel that is broken, because it should be
able to emulate normal Unix filesystem properties on NFS (ie
NFS should appear just the same as other filesystems).
Brian May <bam@snoopy.apana.org.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/