You are welcome to reproduce this problem on a non-Reiserfs file
system. Until then I will ignore the problem report.
According to the logging, the readdir() system library routine
returns a pathname that consists of one non-printable character.
Not surprisingly, there is no file system object with that name.
It looks like a directory locking bug in the Reiserfs file system
code that causes it to look at the wrong information.
Wietse
J?rg Spilker:
> Hello,
>
> here a part of my syslog:
>
> Jun 30 11:33:04 daolin postfix/smtpd[2310]: 1F1101536:
> client=localhost[127.0.0.1]
> Jun 30 11:33:04 daolin postfix/cleanup[2193]: 1F1101536:
> message-id=<[EMAIL PROTECTED]>
>
> Jun 30 11:33:04 daolin kernel: vs-9020: reiserfs_readdir things are
> moving under hands. Researching..
> Jun 30 11:33:04 daolin postfix/qmgr[1566]: fatal: scan_dir_push: open
> directory incoming/6/7/?: No such file or directory
> Jun 30 11:33:04 daolin ip-up: reading message 29 of 31 (2988 octets) ..
> flushed
>
> i found these kind of messages typically 1-2 times a day in my logs. I'm
> not sure if the reiserfs message has anything to do with the postfix
> message. The appear as a pair everytime. A reiserfsck on my var
> partition (which is an LVM device) doesn't show any problems.
>
> Greetings, Joerg
> -
> To unsubscribe, send mail to [EMAIL PROTECTED] with content
> (not subject): unsubscribe postfix-users
>
>
