[Debtags-devel] libtagcoll updates

Erich Schubert Erich Schubert <erich.schubert@gmail.com>
Tue, 5 Apr 2005 03:35:19 -0700

> *OT* (only for my understanding of Linux):
> Does this mean that as long as a file is opened, a deleted file is not
> really deleted (i.e. the occupied blocks are not released)?

Yes, in my experience thats correct. I guess it would cause a lot of
trouble otherwise.
Judging from this I also assume you can delete a file that is write-locked.

After all, it is not deleting. it is unlinking. a file can be linked
in multiple places.
So if we have a file and a hard link to it, and some process has
opened the file at its "first" location - any reason why removing the
other link should not be allowed?

On another related question: is this a source for lost+found files?
"unlinked inodes" - I guess that this will be a typical case. Does
this also happen with journalled filesystem, and what is done to
prevent it? Some unlinked-open-inodes list?

best regards,
Erich Schubert
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
  To understand recursion you first need to understand recursion.   //\
  Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt f=FCr   V_/_
        eine Stunde wie eine Heimat aus. --- Herrmann Hesse