Re: [Evolution] Lots of questions



On Mon, 2006-05-08 at 07:08 +0200, DaffyDuke wrote:
Hello,


Here is a lot of questions I had with evolution 2.4 . They are still there
with the upgrade in 2.6 (Debian Unstable) :

1- How to desactivate full snapshot of messages over IMAP ? I absolutely
don't need in local and for now, evolution is unusable cause local
filesystem is full :
daffy colerpia:~$ df -h .evolution/
Sys. de fich.         Tail. Occ. Disp. %Occ. Monté sur
/dev/hda8             1,2G  907M  198M  83% /home
daffy colerpia:~$ df -i .evolution/
Sys. de fich.         Inodes   IUtil.  ILib. %IUti. Monté sur
/dev/hda8             153280  153056     224  100% /home

I Can't send any mail cause it tries to write in draft folders, where
there is not enough space. If i purge every mail folders in my
.evolution/mail , they are retrieved from imap servers at the first
launched.
I "*really*" need to desactivate offline mode please.

This has nothing to do with Offline mode. If you are sending a message
you need to go online and Evo will immediately update your cache.
There's no way to stop this AFAIK.

Note that you can keep your Drafts folder on the IMAP server
(Edit->Preferences>->Mail Accounts-><account>->Defaults). I do this so I
can work on a draft from more than one location.

What's probably affecting you is running out of Inodes rather than
running out of space (though space is also low). Since Evo caches
headers of every message in every folder you subscribe to, it needs to
be able to create local files even if it's not reading the message
bodies. Even a moderately large folder could easily use up the 224
inodes you have left. All you can do is turn off the message preview
pane (View->Message Preview or Ctrl-M) which will prevent fetching
bodies until you explicitly open a message, and/or unsubscribe any
folders you don't really need.

Your other options are (in order of preference):

1) Get a bigger disk; 1.2G is *so* 1990's :-)
2) Move .evolution to another existing local filesystem with more space
and leave a symbolic link in your home directory.
3) Dump the /home filesystem to a backup medium, mkfs /home with more
inodes, and restore. I would guess you have a lot of small files so the
default number of inodes is probably not enough. See mkfs(8).
4) Dump /home as before and mkfs /home with a filesystem that assigns
inodes on demand, such as ReiserFS.

However 3 and 4 are only palliatives. If you use Evo seriously you are
definitely going to run into this problem again.

poc




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]