Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72B449C90 for ; Thu, 9 Feb 2012 15:10:31 +0000 (UTC) Received: (qmail 63405 invoked by uid 500); 9 Feb 2012 15:10:29 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 62887 invoked by uid 500); 9 Feb 2012 15:10:29 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 62673 invoked by uid 99); 9 Feb 2012 15:10:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 15:10:29 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2012 15:10:20 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 1134D1AC685 for ; Thu, 9 Feb 2012 15:10:00 +0000 (UTC) Date: Thu, 9 Feb 2012 15:10:00 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <750093963.19591.1328800200071.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HADOOP-8042) When copying a file out of HDFS, modifying it, and uploading it back into HDFS, the put fails due to a CRC mismatch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204576#comment-13204576 ] Hadoop QA commented on HADOOP-8042: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12513962/HADOOP-2048.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 eclipse:eclipse. The patch built with eclipse:eclipse. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/578//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/578//console This message is automatically generated. > When copying a file out of HDFS, modifying it, and uploading it back into HDFS, the put fails due to a CRC mismatch > ------------------------------------------------------------------------------------------------------------------- > > Key: HADOOP-8042 > URL: https://issues.apache.org/jira/browse/HADOOP-8042 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 0.24.0, 0.23.1 > Environment: KR at Yahoo > Reporter: Kevin J. Price > Assignee: Daryn Sharp > Priority: Critical > Attachments: HADOOP-2048.patch, HDFS-2777.patch > > > Performing an hdfs -get on a file, modifying the file, and using hdfs -put to place the file back into HDFS results in a checksum error. It seems that the problem is a .crc file being generated locally from the -get command even though the -crc option was NOT specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira