On Wed, Aug 18, 2010 at 11:25:25 +0200, Tollef Fog Heen wrote: > ]] Tino Keitel > > | I just got a suspend failure due to a hanging updatedb.mlocate. The reason > | seems to be a hanging NFSv4 mount caused the server being switched off: > > If you can reproduce this, any chance of a backtrace from the updatedb > process?
I saw this several times already. I usually run into this if I have NFS mounted, and my laptop with mlocate is in a different network or the NFS server is down. Wouldn't I need a debug version of updatedb to create a backtrace?? Regards, Tino -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
