fsck or file system problems?

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

I've been having problems with laptop crashes on suspend/resume
(amd64-current on a Thinkpad T61), but what makes them worse is that
the automatic fsck often fails.  Invariably, the problems are with the
contents of /var/tmp/orbit-smb and /var/tmp/FvwmCommand*.  The former
is full of Unix domain sockets; the latter are named pipes.  Fsck
complains that they're "unallocated".  Should fsck have problems with
these?  Should the file system code be doing something different to
prevent the problem?


                --Steve Bellovin, http://www.cs.columbia.edu/~smb