gjournal on 6.2: Cannot delete /var/.deleted/#613759

[Eric Anderson]

On Nov 9, 2007, at 4:47 AM, Andriy Gapon wrote:

> on 08/11/2007 12:24 Andriy Gapon said the following:
>> I use gjournal6.patch on FreeBSD 6.2 amd64 system.
>>
>> Everything was perfect until today when I got some minor problems  
>> from
>> gjournal. While building a port, compilation aborted with an error  
>> that
>> said something like the following (I didn't save the message,
>> unfortunately): "can not create temporary file: interrupted system  
>> call".
>> I had to restart compilation several times because of such errors and
>> eventually it finished successfully. Along the compilation errors the
>> following message appeared in system log:
>> UFS_GJGC: Cannot delete /var/.deleted/#613759 (error=2)
>> UFS_GJGC: Cannot delete /var/.deleted/#1202391 (error=2)
>> UFS_GJGC: Cannot delete /var/.deleted/#1202391 (error=2)
>> UFS_GJGC: Cannot delete /var/.deleted/#1202390 (error=2)
>> UFS_GJGC: Cannot delete /var/.deleted/#1202390 (error=2)
>>
>
> Well, given that errno 2 is ENOENT, it is interesting what happens  
> here.
> Entry appearing twice on the list of GC items, name clash, something
> else ? Is this something harmless or a result of a more serious  
> issue ?
>
> My guess is that it could be a result of fast creation and deletion of
> some tmp files, so that inode number is reused before an entry is
> actually deleted from .deleted and thus there is a name clash.
> Should be harmless if this is true. Or not ?



When inodes are reused, their gen count should go up (or NFS handles  
would get broken quickly).  The file is probably being removed in- 
between the readdir and the remove.

Eric