On Fri, Aug 07, 2015 at 10:33:17AM +0200, Daniel Pocock wrote: > > You are not working on a NFS/CIFS or BTRFS filesystem? > > It is a BtrFs filesystem accessed over NFS > > It has been working this way for a long time > > I checked the BtrFs filesystem and it definitely has free space and free > metadata space (I understand there can be problems when these fill up > and people don't realize it)
There is also #757199, that is BTRFS related. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757199 Maybe you find some similarity to your behavior. > Even if there is something corrupt, why can't Icedove create a new > profile or give an error to explain where it is stuck? Well, that's a common problem of the main software public interesst out there. The variety of possibilities is much wider on Linux platforms than on Windows. And unfortunately Windows users are the bigger part of users. There are many many small issues living for more than five years ... And Thunderbird is just again on the way to get the problems summarized and solved after the loss of main support by the Mozilla Coorporation. We can't do much here, the code base is just too big to make anything useful in my sparse free time. Sorry, but I can't make any promisses here. > Let me see if there is a way to summarize what it is trying to access > > In some cases it is trying to access things which don't exist, e.g. > searching for a particular file in various places. Some of these > accesses to $HOME appear to be from libraries rather than Icedove itself. Could you please check if you move the profile to a "normal" local filesystem problems are gone? I think the behavior is more or less the same as on bug report #757199. Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
