Re: fatal error: failed to mmap new message file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 27 Nov 2011, Adam Tauno Williams wrote:

> On Sun, 2011-11-27 at 12:14 -0500, Adam Tauno Williams wrote:
>> I updated one of my production boxes to Cyrus IMAPd 2.4.12 [using
>> Simon's excellent packages]
>> On my test box / replica I was able to reconstruct all the mailboxes
>> But [of course] on the production box I have a few mailboxes [important
>> ones, of course] that fail a reconstruc
>> $ /usr/lib/cyrus-imapd/reconstruct -r user.steve
>> fatal error: failed to mmap new message file
>> $ /usr/lib/cyrus-imapd/reconstruct -r user.barnosky
>> fatal error: failed to mmap new message file
>> Reconstructing other mailboxes is working.  Hints / Tips?  reconstruct
>> doesn't seem top have a verbose / debug switch.
>
> In the log file I see -
>
> Nov 27 12:36:23 sardine reconstruct[9524]: seen_db: user barnosky
> opened /var/lib/imap/user/b/barnosky.seen
> Nov 27 12:36:23 sardine reconstruct[9524]: IOERROR: mapping new message
> file: No such device

I assume there is some bad message...  Maybe you can run reconstruct under 
strace to see which message file (if any) it is having trouble with.

 	Andy
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux