I'm not sure but I would imagine that the inode isn't filled with zeroes.
The directory entry in a/b for 'c' is removed and the inode is deallocated
(in-core copy and disk copy) along with any blocks (which I assume in this
case are none). The list of free inodes and blocks is then updated. So my
guess is that the inode isn't cleared to zero, the reference to it is
simply deleted so that it can be re-used by another file.

-Sid.

On Thu, 27 May 2004, Alexandr Kovalenko wrote:

> I have one simple question:
>
> 1. UFS1
>
> 2. Sequence:
>
> $ mkdir a
> $ mkdir a/b
> $ touch a/b/c
> $ rm -rf a/b
>
> The question is: does inode of file 'c' being cleared (e.g. filled with
> zeros or something like that) or not?
>
> --
> NEVE-RIPE, will build world for food
> Ukrainian FreeBSD User Group
> http://uafug.org.ua/
> _______________________________________________
> freebsd-fs@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
>

_______________________________________________
freebsd-fs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"