From patchwork Wed Feb 9 13:03:27 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Lukas Czerner X-Patchwork-Id: 82458 Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id AA625B6F12 for ; Thu, 10 Feb 2011 00:03:39 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754137Ab1BINDg (ORCPT ); Wed, 9 Feb 2011 08:03:36 -0500 Received: from mx1.redhat.com ([209.132.183.28]:15562 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754755Ab1BINDg (ORCPT ); Wed, 9 Feb 2011 08:03:36 -0500 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p19D3ZGg013475 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 9 Feb 2011 08:03:35 -0500 Received: from dhcp-27-109.brq.redhat.com (dhcp-1-233.brq.redhat.com [10.34.1.233]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p19D3TC7015291; Wed, 9 Feb 2011 08:03:33 -0500 From: Lukas Czerner To: linux-ext4@vger.kernel.org Cc: tytso@MIT.EDU, lczerner@redhat.com, adilger@dilger.ca Subject: [PATCH v2 2/2] mke2fs: use binary units in the man page Date: Wed, 9 Feb 2011 14:03:27 +0100 Message-Id: <1297256607-4654-2-git-send-email-lczerner@redhat.com> In-Reply-To: <1297256607-4654-1-git-send-email-lczerner@redhat.com> References: <1297256607-4654-1-git-send-email-lczerner@redhat.com> X-Scanned-By: MIMEDefang 2.67 on 10.5.11.11 Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org (v2: do not spell units - mebibytes etc... - but rather use just abbrev.) Decimal units (kilobyte 10^3, megabyte 10^6 etc...) were used in mke2fs manual page, however they was really meant to be binary units (kibibyte 2^10, mebibyte 2^20 etc...), so change the man pages to reflect that fact, even if it sounds weird. Signed-off-by: Lukas Czerner Reviewed-by: Eric Sandeen --- misc/mke2fs.8.in | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/misc/mke2fs.8.in b/misc/mke2fs.8.in index e093be0..7933dca 100644 --- a/misc/mke2fs.8.in +++ b/misc/mke2fs.8.in @@ -354,9 +354,9 @@ The following journal options are supported: .BI size= journal-size Create an internal journal (i.e., stored inside the filesystem) of size .I journal-size -megabytes. +MiB. The size of the journal must be at least 1024 filesystem blocks -(i.e., 1MB if using 1k blocks, 4MB if using 4k blocks, etc.) +(i.e., 1MiB if using 1024 byte blocks, 4MiB if using 4096 byte blocks, etc.) and may be no more than 102,400 filesystem blocks. @JDEV@.TP @JDEV@.BI device= external-journal @@ -633,21 +633,21 @@ using a comma separated list. If this option is is not specified, .B mke2fs will pick a single default usage type based on the size of the filesystem to -be created. If the filesystem size is less than or equal to 3 megabytes, +be created. If the filesystem size is less than or equal to 3 MiB, .B mke2fs will use the filesystem type .IR floppy . If the filesystem size is greater than 3 but less than or equal to -512 megabytes, +512 MiB, .BR mke2fs (8) will use the filesystem type .IR small . -If the filesystem size is greater than or equal to 4 terabytes but less than -16 terabytes, +If the filesystem size is greater than or equal to 4 TiB but less than +16 TiB, .BR mke2fs (8) will use the filesystem type .IR big . -If the filesystem size is greater than or equal to 16 terabytes, +If the filesystem size is greater than or equal to 16 TiB, .BR mke2fs (8) will use the filesystem type .IR huge .