[OT] Re: [Debtags-devel] libtagcoll updates
Tue, 05 Apr 2005 13:35:35 +0200
sorry for the incomplete mail before..
I don't know much about this but I can speak from some bad
> On another related question: is this a source for lost+found files?
> "unlinked inodes" - I guess that this will be a typical case.
I got my lost+found filled up with 1.5 GB after running reiserfsck after
what seemed like a massive failure in ReiserFS (btw. this happend short
after a kernel update from 2.6.7 to 184.108.40.206 - but I don't know if this
was the reason).
> this also happen with journalled filesystem,
How does deleting work anyways? I've looked through my notes and think
there is a "block bitmap" (or at least there was in ext2fs) which marks
the block in use. If a program fails to toggle this bit when the last
inode pointing to this block is deleted (or more likely the OS does),
this would lead to a unreferenced (lost) datablock.
On the other hand there is the filename to inode mapping. Deleting a
file without deleting the inode it is referring to would lead to an
unreferenced (lost) inode floating around.
Is this correct?