100687 - nsOutputStream: no write errors (like disk full) returned

Status: RESOLVED FIXED

(MailNews Core :: Backend, defect)

Description

[Jean-Francois Ducarroz]

While trying to fix bug 57902, I discovered that neither write, flush, failed or
close return an error when we try to write into a disk out of space.

We need a way to test this condition in order to insure that all the data has
been  correctly written to disk.

Comment 1

[benc]

Should I mark this for all-plats?

Comment 2

[Doug Turner (:dougt)]

which nsOutputStream are you talking about?  I believe that you are using the
stream based on nsFileSpec.  Since nsFileSpec and friends are obsolete, I am
marking as wont-fix.  Please update to use nsFileOutputStream.

Comment 3

[benc]

I don't suppose there is an easy way to find out who else is using this?

Comment 4

[benc]

Jean-Francois: can you answer dougt's question so I can clean up this bug?

Comment 5

[Jean-Francois Ducarroz]

I am using nsOutputFileStream. I did a lxr search on nsFileOutputStream but
cannot find it. I did couple of other search but I cannot figure out which one
to use. Doug, can you advise...

Anyway, I'll reassign this bug to myself and use it as a reminder to change
interface.

Comment 6

[Jean-Francois Ducarroz]

.

Comment 7

[benc]

-> mailnews If this is your use of an interface, then, as I understand it, this
is some kind of mailnews bug.

Comment 8

[derek fong]

Not sure if this is related, but my bookmarks file just got hosed after I quit
Mozilla 1.1 on Mac OS X 10.2 with only 11k of disk space remaining (the
bookmarks file itself was well over 65k).  IMO, this should be marked critical
because of the serious data loss that can (and does) occur.

Comment 9

[Tuukka Tolvanen (sp3000)]

comment 8 sounds like bug 86501, which should've been fixed since 2002-06. see
also bug 163899 bug 153713

Comment 10

[bram-mertens]

Can this be the same reason why no error is returned when a print to file is directed to a directory that is not writable to the user running FireFox (1.5)?

I just lost several confirmation pages because of this (I usually print them to file for future reference).  I only discovered this after trying to find on of the files.

This is on Debian GNU/Linux.  I am still looking for a way to reproduce this on Windows but I'll access to a machine with a non-privileged user account to test this.

Comment 11

[Andrew Schultz]

nsOutputStream is no longer used thanks to bug 33451

Comment 13

[bram-mertens]

when printing to a file in a directory not writable by the user still no error is thrown.

Should I file a new bug for this?

Using Mozilla Firefox 2.0.0.11 on Ubuntu 7.04 "Feisty Fawn".