[Dovecot] Unbreakable NFS locking issues...

[Rod Treweek]

Hi all,

I've got an isolated test environment set up now, and am trying to figure
out how to get the index files to populate.  So far, I cannot seem to get
them to appear in the /usr/local/dovecot/indexes directory as referenced
below.  Here is the sql string:

[root at post-app2 /usr/local/etc]# grep -v '^ *\(#.*\)\?$' dovecot-mysql.conf
driver = mysql

password_query = SELECT username as user, password,
concat('/NFS1MAILDIR/mailSysV2/',
maildir) as userdb_home, concat('maildir:/NFS1MAILDIR/mailSysV2/',maildir,
':INDEX=/usr/local/dovecot/indexes/',maildir) as userdb_mail, 143 AS
userdb_uid, 143 AS userdb_gid, concat('*:storage=', floor(quota*1024)) AS
quota_rule FROM mailbox WHERE username = '%u' AND active = '1'

user_query = SELECT concat('/NFS1MAILDIR/mailSysV2/', maildir) as home,
concat('maildir:/NFS1MAILDIR/mailSysV2/', maildir) as mail,
concat('maildir:/NFS1MAILDIR/mailSysV2/',maildir,
':INDEX=/usr/local/dovecot/indexes/',maildir) as mail_location, 143 AS uid,
143 AS gid, concat('*:storage=', floor(quota*1024)) AS quota_rule FROM
mailbox WHERE username = '%u' AND active = '1'
[root at post-app2 /usr/local/etc]#

I've got mail working more or less, however the indexes simply will not
appear in the path referenced above. My suspicion has been that this is
where my nfs locking problems are occurring, as  the indexes are just not
getting populated.  Any ideas?  I gather that the  cacheing done through the
mysql database is desirable as it would tend to speed things up quite a
bit....any ideas on how to pass the index location through the string as
well? Or is this generally regarded as a negligible gain?

Thanks everyone.

-Rod


On Thu, Nov 13, 2008 at 10:22 AM, Rod Treweek <rtreweek at gmail.com> wrote:

> I'm also noticing that the INDEX=/usr/local/mail/indexes/ path is
> completely empty....shouldn't this get populated if the config is getting
> read properly?
>
>
> On Thu, Nov 13, 2008 at 9:24 AM, Rod Treweek <rtreweek at gmail.com> wrote:
>
>> Thanks for the response.  I also forgot to mention that this is on FreeBSD
>> 6.3. Not sure if that makes a difference.
>>
>>
>> On Wed, Nov 12, 2008 at 4:07 PM, Seth Mattinen <sethm at rollernet.us>wrote:
>>
>>> Rod Treweek wrote:
>>>
>>>>    Yeah, Sorry, still kind of figuring out list protocol. Thanks for the
>>>> responses.
>>>>
>>>> I've not built this system, but I've inherited the responsibility of
>>>> maintaining it, so I'm still kind of trying to gradually learn about how
>>>> everything works together.
>>>>
>>>> I think that the main things are:
>>>>
>>>> fcntl; pretty sure that dotlock is what we should be using, however, I
>>>> was
>>>> under the impression that lockd would/could deal with the file locking
>>>> issues, if it were present on both client and server.
>>>>
>>>>
>>> Maybe, maybe not. I'd try dotlock and see if it helps.
>>>
>>> ~Seth
>>>
>>
>>
>