-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 4 Dec 2009, Paul Ezvan wrote:

Dec  4 12:54:00 gen1 dovecot: IMAP(paul):
maildir_file_do(/home/paul/Maildir/.Travail.Linux.Arch
Linux/cur/1224250603.M73770P8724.gen0:2,): Filename keeps changing

It is always the same filename.

cat the file says that it doesn't exist.

When I do "ls Maildir/.Travail.Linux.Arch Linux/cur/" it says "ls:
cannot access 1224250603.M73770P8724.gen0:2,: No such file or
directory", maybe a filesystem error ?

On Fri, 4 Dec 2009, Paul Ezvan wrote:

ls "Maildir/.Travail.Linux.Arch Linux/cur/" | head -n 2
ls: ne peut accéder Maildir/.Travail.Linux.Arch
Linux/cur/1224250603.M73770P8724.gen0:2,: Aucun fichier ou dossier de ce
type
1224250603.M73441P8724.gen1:2,S
1224250603.M73442P8724.gen1:2,S

Er, I don't get it, you issue

ls "Maildir/.Travail.Linux.Arch Linux/cur/"

and you get the error:

ls: ne peut accéder Maildir/.Travail.Linux.Arch
 Linux/cur/1224250603.M73770P8724.gen0:2,: Aucun fichier ou dossier de ce
type

(you've translated into in the other post: no such file or directory)

??

If so, I would:

a) check for dangling symlinks,
b) check for funny characters in the name ".Travail.Linux.Arch Linux", e.g. line break, tab, ...
c) umount / mount the file system if remote, to reset the internal cache
d) make a file system check

Otherwise, I suppose you should chdir into "Maildir/.Travail.Linux.Arch Linux/cur/" and perform ls -ld 1224250603.M73770P8724* Because Timo's usually very descriptive error messages would lead me to think that the directory entry is either not accessable, but visible (e.g. dangling symlink, read ACL* but no rename ACL, or some other restriction), or that indeed there is such entry, but something is causing it to change some attribute, like keyword, state, etc. everytime, e.g. by by two simultaneous connections.

* With ACL I mean something other than plain Unix permissions, like POSIX ACL, AFS perms, NFS readonly, mandatory locks, SELinux, AppArmor, .... .

Bye,

- -- Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSxz4OXWSIuGy1ktrAQKatgf/YT0dO4oU4tdVlwRETC9PVeCKEudRn7xu
r5bYAhZV8yKA30YaW4VqzeYMh9fSTdrLPPRP5AMchDvvo33gNHx2PLX7QckDpQZx
dpRgUoKO4MTmngyols1+edcfdpSQMu7rnp+xYJoznlIFFFcKrob8JZ/58HgZmW5v
JmjAFRFjxJ0XvI+69aevxak2Xx4W7kgVQcFmVzhMMShhywUEHykUQVq41wGOtWP1
2Rb8erQlpSJVgYFi50OmyMOmAp5hJf3PO9ZNJWcGT76KXnWcnzSywuqfxZ2N/2M0
Q8zzVyDBHd2oTbd70aE9rfzt54xmYYkTwjAzN/+PpmJhJAcuwcL+gw==
=6D7m
-----END PGP SIGNATURE-----

Reply via email to