search for: volatiledir

Hi According to the docs, setting VOLATILEDIR will improve I/O performance when using NFS - but as far as I can see, only vsize lock-files are put here, and little else? Is this correct, and if so are there any plans to move dotlocks etc. to this directory? Thanks. -- Tom

...> installations would be to switch to sdbox/mdbox. Other than that, I > don't remember there being anything important that could be moved > there. Maildir locks yes, switching format is not a procedure I feel comfortable with :) Would it be possible to move the maildir/mbox locks to VOLATILEDIR? -- Tom Sommer

...n that, I >>>>> don't remember there being anything important that could be moved >>>>> there. >>>> Maildir locks yes, switching format is not a procedure I feel comfortable with :) >>>> Would it be possible to move the maildir/mbox locks to VOLATILEDIR? >>> Sure it would be possible, but it's such a low priority for us that I >>> doubt we'll be implementing it. >> Might try and look into it myself. > > Something like this? See attached.<volatile-dotlock.patch> Looks like it works. But could you: 1) A...

...han that, I >>> don't remember there being anything important that could be moved >>> there. >> >> Maildir locks yes, switching format is not a procedure I feel >> comfortable with :) >> >> Would it be possible to move the maildir/mbox locks to VOLATILEDIR? > > Sure it would be possible, but it's such a low priority for us that I > doubt we'll be implementing it. Hrmm okay, fair enough. Seems like a small task though. Might try and look into it myself.

Hello, it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line: mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are the...

On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote: > > Hi > > According to the docs, setting VOLATILEDIR will improve I/O performance when using NFS - but as far as I can see, only vsize lock-files are put here, and little else? Right. I think also autoexpunge locking. > Is this correct, and if so are there any plans to move dotlocks etc. to this directory? What dotlocks? I guess mbox and Maild...

...to switch to sdbox/mdbox. Other than that, I >> don't remember there being anything important that could be moved >> there. > > Maildir locks yes, switching format is not a procedure I feel comfortable with :) > > Would it be possible to move the maildir/mbox locks to VOLATILEDIR? Sure it would be possible, but it's such a low priority for us that I doubt we'll be implementing it.

...don't remember there being anything important that could be moved >>>> there. >>> >>> Maildir locks yes, switching format is not a procedure I feel >>> comfortable with :) >>> >>> Would it be possible to move the maildir/mbox locks to VOLATILEDIR? >> >> Sure it would be possible, but it's such a low priority for us that I >> doubt we'll be implementing it. > > Might try and look into it myself. Something like this? See attached. -------------- next part -------------- A non-text attachment was scrubbed......

...for me writing to the list, I'm trying to change the > > location into which the Dovecot's locks are done reserving a special > > temporary directory on an other partition, then adding to the > > dovecont.conf the line: > > > > mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u > > > > so that through the VOLATILEDIR directive the locks should be written in > > this path. > > We observe though that the locks for many users are still done in the > > real maildir (NFS mounted filesystem) as if in some situations this >...

...ome with local disks > 2) When mail storage and INDEX storage are separated Thanks for these changes! Big win for my setup. My servers are not overly stressed, but how much performance gain (using any metric you choose) can one expect from these changes? > + mail_location can now include VOLATILEDIR=<path> parameter. This > is used for creating lock files and in future potentially other > files that don't need to exist permanently. The path could point to > tmpfs for example. This is especially useful to avoid creating lock > files to NFS or other remote files...

Using 2.3.8 and mail_location = maildir:/var/mail/%Ln:CONTROL=/var/lib/dovecot/control/%Ln:VOLATILEDIR=/var/lib/dovecot/control/%Ln:INDEX=/var/lib/dovecot/control/%Ln + also user_query = SELECT ... CONCAT('maildir:/var/mail/', LOWER(u.login), '/:CONTROL=/var/lib/dovecot/control/%Ln:VOLATILEDIR=/var/lib/dovecot/control/%Ln:INDEX=/var/lib/dovecot/control/%Ln') AS mail, ... but I not...

...it's the first time for me writing to the list, I'm trying to change the > location into which the Dovecot's locks are done reserving a special > temporary directory on an other partition, then adding to the > dovecont.conf the line: > > mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u > > so that through the VOLATILEDIR directive the locks should be written in > this path. > We observe though that the locks for many users are still done in the > real maildir (NFS mounted filesystem) as if in some situations this > instruction is not effec...

As workaround, you can either use VOLATILEDIR setting for maildir, or you can set maildir_stat_dirs=yes in config. Aki On 24.01.2018 14:45, Aki Tuomi wrote: > > Ah seems you have found a bug, apologies. =) > > We'll look into it. > > Aki > > > On 24.01.2018 13:34, Thorsten Hater wrote: >> Well, I have to...

.... New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location = mdbox:/storage1/fast/%{userdb:path}:FULLDIRNAME=iTrNiCs-DBOx-mAiLs:INDEX=/storage1/indexes/vmail/%{userdb:path}:ALT=/storage1/slow/%{userdb:path}:VOLATILEDIR=/tmp/%{userdb:path} userdb:path is generated by the mysql query and ends in something like "2000/6" SQL: CONCAT(u.idAccount, '/', u.idUser) AS userdb_path If I login with imap dovecot is creating the INBOX on the correct path /storage1/fast/2000/6/mailboxes/INBOX btw. it cre...

...elivered-To listen = * lmtp_hdr_delivery_address = original lmtp_rcpt_check_quota = yes login_trusted_networks = 10.0.0.0/30 10.0.0.0/30 10.0.0.0/23 mail_fsync = always mail_gid = vmail mail_home = /srv/mail/%1n/%n mail_location = mdbox:~/dbox:ALT=/srv/archives/%1n/%n/dbox:INDEX=/srv/indexes/%1n/%n:VOLATILEDIR=/var/tmp/dovecot-volatile/%1n/%n mail_plugins = acl mailbox_alias quota fts fts_solr mail_prefetch_count = 20 mail_server_admin = mailto:postmaster at example.com mail_shared_explicit_inbox = yes mail_uid = vmail mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capa...

...oint to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example:...

...oint to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example:...

...doveadm(user at example.com): Debug: Namespace : type=private, prefix=#EXPUNGED/, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=mdbox:/storage1/fast/:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index:FULLDIRNAME=iTrNiCs-DBOx-mAiLs:INDEX=/storage1/indexes/vmail/:ALT=/storage1/slow/:VOLATILEDIR=/tmp/ doveadm(user at example.com): Debug: fs: root=/storage1/fast, index=/storage1/indexes/vmail, indexpvt=, control=, inbox=, alt=/storage1/slow doveadm(user at example.com): Debug: acl: initializing backend with data: vfile doveadm(user at example.com): Debug: acl: acl username = user at example...

...iguration (it is shared storage one, any mdbox on NFS can be accessed by multiple servers, I made it so it's mostly accessed by one, but at certain conditions multiple servers still access mailbox simultaneously). > > So if possible I want to ask few dumb questions: > > - I assume VOLATILEDIR can't be used with configurations where multiple servers access the same mdbox because lockfiles need to be shared as well? Or does this option touch only some (lock)files that do not need to be shared between servers accessing same mailbox? If you're using e.g. Dovecot director, it should...

...oint to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example:...