I recently upgraded a users mail design from iNotes6 to mail8. I tried to update the ODS to 48 but receive the following error when attempting to use “compact -c” on the mail file:
23.12.2008 14:14:01 Informational, database design compression is enabled in database mail/abc123.nsf.
23.12.2008 14:14:01 Informational, LZ1 is enabled in database mail/abc123.nsf.
23.12.2008 14:14:01 Error compacting mail/abc123.nsf: Cannot write or create file (file or disk is read-only)
23.12.2008 14:14:01 Database compactor process shutdow
The system is not low on disk space and the permissions are set correctly. I am able to run fixup, convert, normal compact but the copy-style compact continues to give this error. Has anyone run accross this on a linux platform?
Subject: Re: compact -c erros out with Cannot write or create file (file or disk is read-only)
Thanks for the response but this does not apply to this particular situation. The mail file is well under 1 GB and I am running on a Domino 8.0.2 server.
I had the same issue on another Domino Server today that is running SLES 10 and Domino 8.0.2. The permissions on the mail files are set correctly (as far as I know) so I’m not sure why this continues to be an issue.
I have listed the file permissions, the permissions are set per Lotus Support direction:
-rw-r–r-- 1 notes notes 56350976 Jan 5 16:16 abc1234.nsf
Subject: Re: compact -c erros out with Cannot write or create file (file or disk is read-only)
Actually, the problem isn’t specific to a Mail-file being 1GB in-size. Rather, it is specific to the hard/soft limits (i.e. ulimit) governing the UserID which owns that particular File (or in this case, Database).
Are you aware of such-values within the Environment of your Lotus Domino Server?
Have you successfully upgraded other Databases to use ODS48? Were they larger/smaller than this Database?
Are they owned-by the same UserID?
I suggest that you try setting the ulimit to “unlimited” (for testing-purposes) & then try to run “compact -c” again. If the same-results persist, then I recommend a phone-call to IBM Lotus Support.