Save Attachments to full drive results in wrong error message (Write Protect Error) [windows]

UNCONFIRMED
Unassigned

Status

Thunderbird
General
--
critical
UNCONFIRMED
7 years ago
5 years ago

People

(Reporter: Joe Leikhim, Unassigned)

Tracking

(Depends on: 1 bug, {dataloss})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [dupeme])

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 (.NET CLR 3.5.30729) Thunderbird/3.1.7

Twice in past month I have saved e-mail attachments to a hard drive which was at its capacity limit. In the first case the contents of the target directory were damaged and Win XP checkdisk only reduced the contents of lost chains to unrecoverable files. In second case (yesterday) the target drive was damaged at the root directory. I pulled the drive from the system to attempt recovery and replaced with larger drive. This problem caused loss of all data in a 160 GB drive. Fortunately most was backed up after first anomaly. 

In both cases Thunderbird reports that the "target is write protected" and in both cases, TB has apparently opened the file allocation table (I think was FAT) and unable to close properly. This is a serious error. If I am misguided in this being a TB error please help me resolve in the OS. However in both cases, TB was the program being used. my e-mail address is rhyolite@nettally.com and I would appreciate help. Thanks.

Reproducible: Always

Steps to Reproduce:
1. Target drive should be at or near capacity.
2. Open an e-mail with files sufficient to exceed target drive capacity.
3. Attempt to save all attachments. (File/Save Attachments...)
4. Should receive error that target drive is write protected.
5. Target drive will be damaged at root or directory level.

Actual Results:  
4. Should receive error that target drive is write protected.
5. Target drive will be damaged at root or directory level.

Expected Results:  
4a. Should receive error that target drive has insufficient space.
5a. Target drive should not be damaged.

6. I believe the damaged drive was FAT however may have been NTFS. 

my e-mail address is rhyolite@nettally.com and I would appreciate help. Thanks.
(Reporter)

Comment 1

7 years ago
WP Error and damaged file allocation table should be acceptable key words.

Correction the damaged drive was 60 GB.
Keywords: dataloss
(Reporter)

Comment 2

7 years ago
Wow months go by and no one is interested in fixing a critical problem?
(Reporter)

Comment 3

7 years ago
Moved to security as this is a dataloss problem
Component: Toolbars and Tabs → Security
QA Contact: toolbars-tabs → thunderbird

Comment 4

7 years ago
Hi, I will take a look at this issue to figure out the cause of the problem which you saw, assuming that this can be reliably re-created under linux too, 
during the fixing of
 Bug 429827
 Bug 567585 

But if and when can I figure out the cause, we will have to ask someone with Windows skill to eradicate the bug since I don't build and debug Windows versions locally.

Comment 5

7 years ago
I have filed a new bug for linux's case of saving an attachment in an almost full file system.

Bug 663071
Saving an attachment to an almost full filesystem generates an erroneous error message(linux), ...

(Forgot to post to this bug entry!)

In the case of linux, the file system is not corrupted, but it remains full
because a partially written file is left behind, 
and no writing can proceed.

Also, I noticed that it seems that the file descriptor to the partially saved file was not intentionally closed(?) by TB after the error, and it got closed
probably at the exit of TB3.

Given the difference of Windows XP and Linux file systems, the dubious handling of file descriptor when file system becomes full well may be the
cause of file system corruption in the case of linux.

Comment 6

6 years ago
please explain what is "WP Error"?  Windows Protection?

whether it's FAT or NTFS, thunderbird wouldn't access the information directly and therefore any corruption relating this this would have been ultimately caused by the OS
Depends on: 663071
Summary: Save Attachments to full drive results in WP Error and damaged file allocation table → Save Attachments to full drive results in WP Error and damaged file allocation table [windows]

Comment 7

6 years ago
Ah, WP=write protect.

I don't believe Thunderbird "damaged file allocation table". So this bug could be duped a "wrong error message" bug.  But Bug 663071 is linux-only?
Component: Security → General

Updated

6 years ago
Summary: Save Attachments to full drive results in WP Error and damaged file allocation table [windows] → Save Attachments to full drive results in Write Protect Error and damaged file allocation table [windows]
Whiteboard: [closeme 2012-08-20][dupeme]
(Reporter)

Comment 8

6 years ago
The operating system is Win XP Home Edition. The bug indeed trashed the drive somehow. Maybe somebody could reproduce in a "sandbox" environment?

Updated

6 years ago
Whiteboard: [closeme 2012-08-20][dupeme] → [dupeme]
(In reply to Joe Leikhim from comment #8)
> The operating system is Win XP Home Edition. The bug indeed trashed the
> drive somehow. Maybe somebody could reproduce in a "sandbox" environment?

Joe, I believe many bugs in TB, but I agree with Wayne's comment 7 that it is impossible that TB is responsible for damage or even mess-up to FAT. Simply because TB cannot possibly access FAT unless through the OS, so the OS needs to guard anything in that realm -> adjusting summary
So the only thing TB can do is to check in advance about available disk space and then come up with a more descriptive warning message.

(In reply to Wayne Mery (:wsmwk) from comment #7)
> I don't believe Thunderbird "damaged file allocation table". So this bug
> could be duped a "wrong error message" bug.  But Bug 663071 is linux-only?

So I'll morph this to be about the error message in windows, as it needs separate fix for each OS.
Might still be a dupe.
Summary: Save Attachments to full drive results in Write Protect Error and damaged file allocation table [windows] → Save Attachments to full drive results in wrong error message (Write Protect Error) [windows]
You need to log in before you can comment on or make changes to this bug.