On Tue, Jul 26, 2005 at 01:24:12PM +0200, Zeljko Vrba wrote:
> Pavel Cahyna wrote:
> >
> >You also said that you can't do even a ls -l when this happens. Where is
> >that ls -l command blocked at that moment?
> >
> That 'ls -l blocks' is conditional. I have the large mmaped file on
> /mnt/data (a separate filesystem). ls -l in /usr works, ls -l on

So, your previous claims that "everything just stops" was a bit exaggerated
:-)

> /mnt/data blocks. I guess because the large mmaped file is exactly in
> /mnt/data. ls is also blocked in vnlock.

Interesting. By "exacly in", you mean in the /mnt/data directory, right?

What would happen if you did ls -l in the same filesystem, but in a
different directory than /mnt/data?

Bye	Pavel