<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi,<br class=""><br class="">you can use INDEX=/writable/path/%u in your mail_location setting to define location for the required index data when importing.<br class="">Also possibly you would need to define writable location for CONTROL and VOLATILEDIR. <br class=""><br class="">see <a href="https://wiki.dovecot.org/MailLocation" class="">https://wiki.dovecot.org/MailLocation</a><br class=""><br class="">Sami<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 14 Jan 2019, at 11.23, hby <<a href="mailto:hby@hby.hu" class="">hby@hby.hu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">Dovecot version: 2.2.34</div><div dir="ltr" class=""><br class=""></div><div class="">doveadm import tries to call open() on the source indexes/logs of mdbox data, but even if it should work as it is just a read-related call, it fails on read-only filesystems.</div><div class=""><br class=""></div><div class="">The main use case for read-only filesystem is restoring from backup: the massive deduplicated backup data is exposed using FUSE. For deduplication to work efficiently, we have to backup the whole mail storage and thus the only way to handle the restore to mount the whole data.</div><div class=""><br class=""></div><div class="">I would like to ask for some proper solution for this problem.</div><div class=""><br class=""></div><div class="">Suggestions: first, the doveadm import should never modify the indexes, and second: the open() calls should respect the read-only filesystem and should fall back to "r" flag when using open.</div><div class="">The problem goes further when using SIS (which goes beyond multiple terrabytes).<br class=""></div><div class=""><br class=""></div><div class="">The only workaround currently is to export the whole mdbox data to a writeable storage, and parametrize the import command to use that and the mounted SIS data separately for import...which is just problematic, ugly and error prune.</div><div class=""><br class=""></div><div class="">Thank you for the continous work on dovecot, I hope you get this feedback in a good way.</div></div>
</div></blockquote></div><br class=""></body></html>