Zimbra

borispr · #1 (**permalink**) 03-26-2008, 06:21 AM

I want to create a special account to hold shared archive folders for users. And I want to store this messages on network drive.
I have mounted network storage to /opt/zimbra/store/0/14/msg (user's folder) with correct attributes, uid and gid. (zimbra:zimbra, 750 for folder and 640 for files). Zimbra successfully creates a subfolder "0" in it, but can't create a message file in it. I don't understand why.
The idea is to remove this user from current filesystem to another filesystem where much more space.

uxbod · #2 (**permalink**) 03-26-2008, 06:46 AM

what if you do the following :-

Code:

su - zimbra
echo "TEST" > /opt/zimbra/store/0/14/msg/0/testfile

does the file get created ? does it have the correct permissions ? what type of network share is it ie. samba or nfs etc ?

borispr · #3 (**permalink**) 03-26-2008, 08:27 AM

yep, I've tried to create file under zimbra (touch /opt/zimbra/store/0/14/msg/0/1.txt was successful)

storage connected via samba
mount -t cifs -o rw,username=user,password=pass,uid=501,gid=501,fil e_mode=0640,dir_mode=0750 //192.168.10.14/mail$ /opt/zimbra/store/0/14/msg

uxbod · #4 (**permalink**) 03-26-2008, 08:33 AM

well thats good

could you check the Log Files - Zimbra :: Wiki especially mailbox.log for any error messages please.

borispr · #5 (**permalink**) 03-26-2008, 09:16 AM

now I do experiment with mailbox 87
I have created draft mail (260-100.msg), copied it to tmp, mounted external fs, copied draft back
I can see it in the draft folder, I can open it, but can't save it

here is a log from mailbox.log

Code:

2008-03-26 19:09:06,245 INFO  [btpool0-12] [name=archive-holder@zmail.;mid=87;ip=192.168.11.11;ua=ZimbraWebClient-FF2.0 (Win)/5.0.2_GA_1975.RHEL5;] cache - Initializing folder and tag caches for mailbox 87
2008-03-26 19:09:06,264 INFO  [btpool0-12] [name=archive-holder@zmail.;mid=87;ip=192.168.11.11;ua=ZimbraWebClient - FF2.0 (Win)/5.0.2_GA_1975.RHEL5;] SoapEngine - handler exception com.zimbra.common.service.ServiceException: system failure: IOException while saving draft
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:183)
        at com.zimbra.cs.service.mail.SaveDraft.handle(SaveDraft.java:117)
        at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:208)
        at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:113)
        at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
        at org.mortbay.jetty.Server.handle(Server.java:313)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.io.IOException: Unable to rename /opt/zimbra/store/incoming/1206547052760-62.msg to /opt/zimbra/store/0/87/msg/0/260-102.msg
        at com.zimbra.cs.store.FileBlobStore.renameTo(FileBlobStore.java:297)
        at com.zimbra.cs.mailbox.MailItem.setContent(MailItem.java:1343)
        at com.zimbra.cs.mailbox.Mailbox.saveDraftInternal(Mailbox.java:4169)
        at com.zimbra.cs.mailbox.Mailbox.saveDraft(Mailbox.java:4136)
        at com.zimbra.cs.service.mail.SaveDraft.handle(SaveDraft.java:115)
        ... 30 more

uxbod · #6 (**permalink**) 03-26-2008, 09:26 AM

Hmmm, I wonder if this is a issue with Samba and OpLocks (thinking out loud).

borispr · #7 (**permalink**) 03-26-2008, 09:37 AM

"Unable to rename /opt/zimbra/store/incoming/1206547052760-62.msg to /opt/zimbra/store/0/87/msg/0/260-102.msg"

Original message is 260-100.msg
It tries to save it under name 260-102.msg. Should it be so?
If I rename 260-100 to 260-102 Zimbra doesn't open it.

BTW, file /opt/zimbra/store/incoming/1206547052760-62.msg exists
and manually I can move it to /opt/zimbra/store/0/87/msg/0/260-102.msg