Closed
Bug 280793
Opened 20 years ago
Closed 19 years ago
Warn if local mail folders get close to 4GB
Categories
(MailNews Core :: Backend, defect)
MailNews Core
Backend
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jshin1987, Assigned: Bienvenu)
Details
(Keywords: dataloss)
Attachments
(1 file)
9.15 KB,
patch
|
mscott
:
superreview+
benjamin
:
approval1.8b4+
|
Details | Diff | Splinter Review |
I've seen a few reports of Korean mozilla users that thunderbird can't handle local folders larger than 2GB even on NTFS. This is likely to be a dupe, but my search failed.
Assignee | ||
Comment 1•20 years ago
|
||
I've heard reports of this. I had it working at one point, but it seems like it has regressed. I need to recreate this. I doubt it has anything to do with Korean users, but has to do with a signed/unsigned issue to do with message keys.
Assignee: sspitzer → bienvenu
Summary: mail folder (local) size limit is 2GB even on NTFS? → mail folder (local) size limit is 2GB even on NTFS?
Reporter | ||
Comment 2•20 years ago
|
||
adding cbie because he recently worked on large file handling. Perhaps, his fix for bug 264599 has already fixed this problem unless msgDB/RDF has some more fixes to go beyond 2/4GB size limit (basically, need to use 64bit int) as for Korean users, I just mentioned it because that's where I heard of it. Needless to say, it cannot possibly anything to do with Korean users :-)
Reporter | ||
Comment 3•20 years ago
|
||
sorry for bug spam. if it's something to do with message keys, this must be an issue on all platforms.
OS: Windows XP → All
Hardware: PC → All
Assignee | ||
Comment 4•20 years ago
|
||
yes, it has to do with message keys, and even with my fix, we only go to 4GB, not 2GB. Message keys are 32 bit, and converting them to 64 bits would be challenging...at the time that I fixed things to work with 4GB files, the underlying necko interfaces didn't work with 64 bit values so I didn't take that challenge :-)
Comment 5•20 years ago
|
||
note bug 207400 I'd be happy to fix all necko interfaces that do not support 64-bit ints, especially if they are unfrozen
Assignee | ||
Comment 6•19 years ago
|
||
Jungshik, were these users using 1.0, do you know? I tried this on the trunk, and it worked OK - see bug 207400. This should be working in 1.0 as well.
Reporter | ||
Comment 7•19 years ago
|
||
They said they had problems with 1.0, but they may have meant 4GB. I asked them to clarify and will get back here to report.
Comment 8•19 years ago
|
||
I'm having a similar problem on Linux. My 'About->Mozilla' string is: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Debian/1.7.8-1 And my filters are failing. The filesizes are: 2147512157 May 25 14:37 Mail 0 May 25 14:56 Mail.msf It's not a filesystem issue, I also have a procmail'd version (unfiltered): 3571697366 May 25 14:48 mbox This is from the suite, not thunderbird specifically.
ccurtis0@gmail.com: can you try mozilla trunk instead of the 1.7 branch?
Comment 10•19 years ago
|
||
If a user's Inbox hits the 2G limit, will there be dataloss?
Comment 11•19 years ago
|
||
In my experience on the 1.7 branch, yes: the mail file ends up being corrupted to the point that rebuilding the index file kills everything.
Comment 12•19 years ago
|
||
Unless this code doesn't have the dataloss problem on the trunk that it has on the branch, I'd suggest this block 1.1.
Flags: blocking-aviary1.1?
Keywords: dataloss
Comment 13•19 years ago
|
||
transferring nomination to 1.8b4. If we don't get it there, we don't get it for 1.1
Flags: blocking-aviary1.1? → blocking1.8b4?
Updated•19 years ago
|
Flags: blocking1.8b4? → blocking1.8b4+
Assignee | ||
Comment 14•19 years ago
|
||
on the trunk, the limit is 4GB. I have a patch that warns the user when they're within 1MB of that limit for local folders.
Summary: mail folder (local) size limit is 2GB even on NTFS? → mail folder (local) size limit is 4GB even on NTFS?
Assignee | ||
Comment 15•19 years ago
|
||
Assignee | ||
Updated•19 years ago
|
Attachment #191372 -
Flags: superreview?(mscott)
Updated•19 years ago
|
Attachment #191372 -
Flags: superreview?(mscott) → superreview+
Assignee | ||
Updated•19 years ago
|
Attachment #191372 -
Flags: approval1.8b4?
Comment 16•19 years ago
|
||
Comment on attachment 191372 [details] [diff] [review] warn if local folders get with 1MB of 4GB The wording of the dialog sounded awkward, so I asked MikeB to suggest some alternatives: <beltzner> I got two suggestions: <beltzner> friendly-but-less-specific: <beltzner> The folder %S is full, and can't hold any more messages. To make more room, delete any old or unwanted mail and compact the folder. <beltzner> tecchie-but-exact: <beltzner> The folder %S has reached the maximum possible size (4GB) and can't hold any more messages. To reduce the size, delete any old or unwanted mail and compact the folder.
Attachment #191372 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 17•19 years ago
|
||
I prefer the non-techie one, with one tweak - instead of "To make more room", I'd prefer "To make room for more messages", since there currently isn't any room, so the phrase "more room" isn't quite right.
Assignee | ||
Comment 18•19 years ago
|
||
fixed (in the sense that we warn the user and don't let the get new mail or msg copy run). if and when we support a single msg per file message store, then this won't be an issue.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 19•19 years ago
|
||
We could suggest to create subfolders and move old messages to these subfolders instead of deleting them.
Comment 20•19 years ago
|
||
I haven't tested the patch myself, but I can see that the filesize check is done _before_ the message is received or copied, i.e. it does not take the size of the message being received/copied into account. If I receive/copy a message larger than 1 MB (the warning threshold), wont that cause the file to grow beyond 4GB without warning the user? BTW I suggest leaving this bug open until the problem described in the summary is eventually fixed.
Assignee | ||
Comment 21•19 years ago
|
||
yes, that's true - however, time was short for 1.5 and I wanted to get the new string in before we stop taking new strings. I think that's an edge case we can worry about in beta - things should be much better than they were before. Also, what's important is where the message starts, so as long as it starts before the 4GB mark, it should be OK.
Updated•17 years ago
|
Summary: mail folder (local) size limit is 4GB even on NTFS? → Warn if local mail folders get close to 4GB
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•