Thanks Bron / list for your reply
I am using cyrus-imapd-2.4.17-6.el6.x86_64 , with ext4 file system .
Just now the issue has been resolved , I found corruption with inode level and few emails. Some email was converted to binary file.
Due to which few mailboxes was corrupted . Delivery or access of such mailbox was getting failed and Segmentation fault & core file was getting generated .
After identifying such mailbox manually , i moved those to other path and removed all cyrus.* files , recreated the new mailbox and moved that all non-corrupted emails and reconstruct the same. Its seem my issue is resolved for now . For next 1/2 days will monitor the flow and after that will shift the data with new LUN . I Will verify the badblocks and will re-format the LUN with new fresh filesystem.
Do you know what could be the reason for below scenario :--
------------------------------------------------------------------------
I found one interesting point with core.xxxx files , The sizing of such files with du -sh & ls -lh was showing different .
While doing the same file "cp" or "rsync" it was showing me different size. Also the inodes for "cp" file was less and inodes for "rsync" file was more. With Google I learn that cp & du work differently .
I verified the same with another ext3 partition , but there sizing is showing proper.
My question is , whether its normal behavior or related corrupted inode or file system ? In tune2fs -l , filesystem showing clean.
Below is for reference scenario.
[root@active ~]# rsync -av /hacluster/varlib/imap/core.10236 /hacluster/san-testing/by-rsync/
[root@active ~]# cp -p /hacluster/varlib/imap/core.10236 /hacluster/san-testing/by-cp/
[root@active ~]# ls -lh /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
-rw------- 1 cyrus mail 1.3G Jun 16 08:19 /hacluster/san-testing/by-cp/core.10236
-rw------- 1 cyrus mail 1.3G Jun 16 08:19 /hacluster/san-testing/by-rsync/core.10236
[root@active ~]# du -sh /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
3.3M /hacluster/san-testing/by-cp/core.10236 <----- Note this
1.3G /hacluster/san-testing/by-rsync/core.10236
[root@active ~]# md5sum /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
2b66ecf5187fb341e60ba61c92747d0d /hacluster/san-testing/by-cp/core.10236
2b66ecf5187fb341e60ba61c92747d0d /hacluster/san-testing/by-rsync/core.10236
[root@active ~]# cp -p /hacluster/varlib/imap/core.10236 /hacluster/san-testing/by-cp/
[root@active ~]# ls -lh /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
-rw------- 1 cyrus mail 1.3G Jun 16 08:19 /hacluster/san-testing/by-cp/core.10236
-rw------- 1 cyrus mail 1.3G Jun 16 08:19 /hacluster/san-testing/by-rsync/core.10236
[root@active ~]# du -sh /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
3.3M /hacluster/san-testing/by-cp/core.10236 <----- Note this
1.3G /hacluster/san-testing/by-rsync/core.10236
[root@active ~]# md5sum /hacluster/san-testing/by-cp/core.10236 /hacluster/san-testing/by-rsync/core.10236
2b66ecf5187fb341e60ba61c92747d0d /hacluster/san-testing/by-cp/core.10236
2b66ecf5187fb341e60ba61c92747d0d /hacluster/san-testing/by-rsync/core.10236
Regards
Jayesh Shinde
On Fri, Jun 19, 2015 at 04:06 AM, Bron Gondwana <brong@xxxxxxxxxxx> wrote:
We're going to need to know at least what version of Cyrus you are running. Loading a core file with gdb and pasting a backtrace might be helpful too.Bron.On Thu, Jun 18, 2015, at 12:40 AM, Jayesh Shinde wrote:Hi ,
I am facing problem with randomly mail delivery to local mailboxes. While doing reconstruct its showing Segmentation fault
Also there lots of core.xxx files created under /var/lib/imap.
-bash-4.1$ /usr/lib/cyrus-imapd/reconstruct -r -f user/amit.badarpur@xxxxxxxxxx
user/amit.badarpur@xxxxxxxxxx
Segmentation fault
And the dmesg is showing error like below .
imapd[7127]: segfault at 7f9092d7ce33 ip 00007f905fc1192e sp 00007fff659f55e0 error 4 in imapd[7f905fbae000+191000]
reconstruct[17981]: segfault at 7f656e112c4b ip 00007f64fdc1380e sp 00007ffff1cf7110 error 4 in reconstruct[7f64fdbdd000+15b000]
reconstruct[19517]: segfault at 7f0ea8ae2c4b ip 00007f0e3494780e sp 00007fff162a79d0 error 4 in reconstruct[7f0e34911000+15b000]
reconstruct[19693]: segfault at 7fa5821b0c4b ip 00007fa50e01580e sp 00007fff2f724aa0 error 4 in reconstruct[7fa50dfdf000+15b000]
lmtpd[6046]: segfault at 7f141270712e ip 00007f13d86c242e sp 00007fff483d6000 error 4 in lmtpd[7f13d867e000+16d000]
lmtpd[3130]: segfault at 7fd68612606f ip 00007fd665e8b42e sp 00007fff9b8595f0 error 4 in lmtpd[7fd665e47000+16d000]
I checked by moving the mailbox from iscsi partition to local drive and simlink the same . But when i do reconstruct again it gives "Segmentation fault"
I checked by doing the gdb the core.xxx files , but not able to got the actual problem.
What could be the problem. Is its related server's Memory or currption on mailbox ?
How can I handle it.
Regards
Jayesh Shinde----Cyrus Home Page: http://www.cyrusimap.org/List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/To Unsubscribe:
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus