Date: Mon, 14 Jul 2003 15:50:10 -0700 (PDT) From: Andy Farkas <andyf@speednet.com.au> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/48435: wierd file system behavior Message-ID: <200307142250.h6EMoAfM015124@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/48435; it has been noted by GNATS.
From: Andy Farkas <andyf@speednet.com.au>
To: "Jin Guojun [NCS]" <j_guojun@lbl.gov>
Cc: Kris Kennaway <kris@freebsd.org>,
<freebsd-gnats-submit@freebsd.org>
Subject: Re: kern/48435: wierd file system behavior
Date: Tue, 15 Jul 2003 08:43:57 +1000 (EST)
I don't think this is a bug. Its what tar does.
A truss of tar when the directory exists, but has no files:
mkdir(0x809b070,0x1ed) ERR#17 'File exists'
unlink(0x809b070) ERR#1 'Operation not permitted'
rmdir(0x809b070) = 0 (0x0)
mkdir(0x809b070,0x1ed) = 0 (0x0)
But when a file exists in the directory:
mkdir(0x809b070,0x1ed) ERR#17 'File exists'
unlink(0x809b070) ERR#1 'Operation not permitted'
rmdir(0x809b070) ERR#66 'Directory not empty'
So it seems tar is removing then creating the directory if it is empty.
--
:{ andyf@speednet.com.au
Andy Farkas
System Administrator
Speednet Communications
http://www.speednet.com.au/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307142250.h6EMoAfM015124>