> > Looks to me like the unlink syscall is somewhat synchronous, and it
> > shouldn't, or does it? For this concrete issue, it could be easily
> > solved by the unlink syscall starting a thread to unlink the big file,
>
> Cosmetics.
>
> $ rm bigfile&
>
> will achieve exactly the same thing at no kernel
> cost...
>
No it won't. Try this in a partition with enough free space:
dd if=/dev/zero of=test bs=1k count=800000
[wait]
rm test &
ls
The last ls won't show inmediately. In fact, it will be blocked till the
rm finishes - which is the behaviour I think we need to suppress...
Try it...
-- Jorge Gonzalez <jorgegv@icai.upco.es> -o) ICAI - Universidad Pontificia Comillas /\\ Administrador de Sistemas _\_v- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/