Amavis

[kollross]

We upgraded to M3 last night and noticed on our spamfilter server disk mem is being mounted several times

/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp

It gets mounted multiple times after boot up
that number also begins to grow

After boot it was mounted 2 times, but after 16 mins of up time it shows thats its been mounted 6 times.
/etc/fstab only shows one entry.

Here is my df

/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp
/dev/ram0 31729 409 31320 2% /mnt/rd
/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp
/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp
/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp
/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp
/dev/shm 153600 264 153336 1% /opt/zimbra/amavisd-new-2.3.3/tmp

[KevinH]

probably a bug from the rename - make sure there's only one line in /etc/fstab, and the mount and umount commands in the start/stop script reference the correct directories.

[kollross]

Thanks kevin.

I got to looking and there was only one entry under my /etc/fstab. That was the first place i checked before i posted. Like I said the weird part was that after a reboot I was at 2 mounts but after a while the number increased which i had no explination for.

I did however find a fix (though i doubt its a permanent fix, more of a getting it to start working after its broke)

I first noticed the problem by doing a zmamavisdctl stop and it said that there was multiple mounts for /opt/zimbra/amavisd-new-2.3.3/tmp

I found simply doing a
umount -l /opt/zimbra/amavisd-new-2.3.3/tmp
for every additional mount removed on instance of the mount. For some reason it does not unmount all of the amavis though so I have to perform it multiple times

umount -l /opt/zimbra/amavisd-new-2.3.3/tmp
df
unmount -l /opt/zimbra/amavisd-new-2.3.3/tmp
df

until there was one remaining mount
I then did a zmamavisdctl stop start again to get the thing scanning.

Very weird.