Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <30026333.52081291230255555.JavaMail.jira@thor>
Date: Wed, 1 Dec 2010 14:04:15 -0500 (EST)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-1524) Image loader should make sure to read
 every byte in image file
In-Reply-To: <4151043.50721291226593421.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hairong Kuang updated HDFS-1524:
--------------------------------

    Attachment: eofImageFile.patch

> Image loader should make sure to read every byte in image file
> --------------------------------------------------------------
>
>                 Key: HDFS-1524
>                 URL: https://issues.apache.org/jira/browse/HDFS-1524
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>            Priority: Blocker
>             Fix For: 0.22.0, 0.23.0
>
>         Attachments: eofImageFile.patch
>
>
> When I work on HDFS-1070, I come across a very strange bug. Occasionally when loading a compressed image, NameNode throws an exception complaining that the image file is corrupt. However, the result returned by the md5sum utility matches the checksum value stored in the VERSION file. 
> It turns out the image loader leaves 4 bytes unread after loading all the real data of an image. Those unread bytes may be some compression-related meta-info. The image loader should make sure to read to the end of file in order for an correct checksum.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.