Re: more about scheduler missing files

[Eugene Crosser <crosser@online.ru>]

And one more information:

root@ajax2:/u/var/spool/postoffice/# ls -l 
total 13722
drwx--l---   2 root     other        512 Apr  7 22:45 TLSclntcache
drwx--l---   2 root     other        512 Apr  7 22:45 TLSsrvrcache
drwxr-s---   2 root     other     380928 Aug 29 16:30 deferred
drwxr-s---   2 root     other        512 Apr  7 22:45 freezer
drwxr-s---   2 root     other    4433408 Aug 29 16:29 postman
drwxrwsrwt   2 root     other      26112 Aug 29 15:57 public
drwxr-sr-x   2 root     other     834560 Aug 29 16:19 q
drwxr-s--- 32767 root     other     834560 Aug 29 16:29 queue
drwxrwsrwt   2 root     other     314368 Aug 29 16:30 router
drwxr-sr-x  28 root     other     129536 Aug 29 16:29 transport

note the number of links of the "queue".

On a working system I have this:

root@ajax1:~/# ls -ld /var/spool/postoffice/queue        
drwxr-s--- 862 root     other      21504 Aug 29 17:03
/var/spool/postoffice/queue
root@ajax1:~/# find /var/spool/postoffice/queue -type d|wc -l
      27
root@ajax1:~/# find /var/spool/postoffice/queue -type f|wc -l
     388

Normally the number of links of a directory is the number ot its
subdirs plus one.  The number that I see looks absolutely insane.
Also note that when you execute link() syscall as root you *can*
make hardlink to a directory, although it becomes hard to manage
after that.  Looks like the scheduler could create wrong links?

Eugene