Uploaded image present blank 8192 byte sections
Closed, DeclinedPublic
Actions

Assigned To

Authored By

	Platonides
	Jul 13 2009, 1:14 PM

Description

[[File:Gogh, Vincent van - Memory of the Garden at Etten (Ladies of Arles).jpg]] was uploaded this morning. The server has it corrupt. Filesize (95.674.940) is correct but sha1 (9bde05a09121148a38c2dcd9b8295a4ca7caa760) is not (should have been ae7b210f9ef765f167fa5c89e3bf460e1be7aa66).

The stored image contains 5 blocks of 8192 bytes of blank content (filled with \0s).
232000- 234000
187A000-187C000
18A6000-18A8000
1EE0000-1EE2000
1EE6000-1EE8000

Obviously, all of these had data in the original one.

I know we're having problems with filesystem disk space. Rejecting the upload for that would be acceptable, but this is not.

I suspect the bug lies at NFS or ZFS.

Marking as critical since this involves data loss.

Version: unspecified
Severity: critical
URL: http://commons.wikimedia.org/wiki/File:Gogh,_Vincent_van_-_Memory_of_the_Garden_at_Etten_%28Ladies_of_Arles%29.jpg

Details

Reference: bz19696

Event Timeline

• bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:41 PM

• bzimport added a project: WMF-General-or-Unknown.

• bzimport set Reference to bz19696.

Platonides created this task.Jul 13 2009, 1:14 PM

That's an interesting failure mode... blocks of 0s sounds like NFS borkage to me.

(Actually, double-checking the file save on upload by checking the sha-1 hash might not be an awful idea.)

This should be fixed by Swift, if it's even still happening (which maybe it isn't)

(In reply to comment #2)

This should be fixed by Swift, if it's even still happening

Changing to WORKSFORME to get rid of deprecated LATER in this case.

Uploaded image present blank 8192 byte sectionsClosed, DeclinedPublicActions

Description

Details

Event Timeline

Uploaded image present blank 8192 byte sections
Closed, DeclinedPublic
Actions