Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 11353 invoked from network); 8 Sep 2010 03:04:51 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Sep 2010 03:04:51 -0000 Received: (qmail 66370 invoked by uid 500); 8 Sep 2010 03:04:49 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 66080 invoked by uid 500); 8 Sep 2010 03:04:46 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 66069 invoked by uid 99); 8 Sep 2010 03:04:46 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Sep 2010 03:04:46 +0000 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zjffdu@gmail.com designates 74.125.82.176 as permitted sender) Received: from [74.125.82.176] (HELO mail-wy0-f176.google.com) (74.125.82.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Sep 2010 03:04:23 +0000 Received: by wyf23 with SMTP id 23so8484804wyf.35 for ; Tue, 07 Sep 2010 20:04:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=jGXO9K/8NJIdOGKMl7bWXc663TnBphaJKRjNMvGBJVE=; b=pfgSqdUKqnr32bEa9xfQuH/+BydLZ9+8iWHMlXd5YKfOda2XyN0V5lV+1kLglVko0+ ShN9LZdKOMsxTdwb6GT819ebyXyikcL0cYMgmHSRaRgiR9/I0/gHg8tQhijVoAGIfNGE wVx1kS+Cn7JKdPNyg2nAQd7IhJyMv3JYGdog0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qltBFino1Rj5lt0mDoNrad63OnXB1plfsTXI1AT1kDC2bj+BBp3Gp2P/DOClUqZQy+ gH8Q9zONw9kIteST+w3IGDZ4+UTcwUHHag1a3sQzjKOValoM0TKCzfZZByFdd/HOp6FK 3VhMwwSzj6RU01TVJXgKLnhQ3NBIa9TUjitjk= MIME-Version: 1.0 Received: by 10.216.11.131 with SMTP id 3mr188917wex.92.1283915038475; Tue, 07 Sep 2010 20:03:58 -0700 (PDT) Received: by 10.216.163.5 with HTTP; Tue, 7 Sep 2010 20:03:58 -0700 (PDT) In-Reply-To: <732954.171.qm@web15901.mail.cnb.yahoo.com> References: <4C84BEF2.3080507@apache.org> <732954.171.qm@web15901.mail.cnb.yahoo.com> Date: Tue, 7 Sep 2010 20:03:58 -0700 Message-ID: Subject: Re: change HDFS block size From: Jeff Zhang To: common-user@hadoop.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Those lagacy files won't change block size (NameNode have the mapping between block and file) only the new added files will have the block size of 128m On Tue, Sep 7, 2010 at 7:27 PM, Gang Luo wrote: > Hi all, > I need to change the block size (from 128m to 64m) and have to shut down the > cluster first. I was wondering what will happen to the current files on HDFS > (with 128M block size). Are they still there and usable? If so, what is the > block size of those lagacy files? > > Thanks, > -Gang > > > > > -- Best Regards Jeff Zhang