From owner-freebsd-fs@FreeBSD.ORG  Tue Aug 23 20:23:17 2011
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5063A106564A
	for <freebsd-fs@FreeBSD.org>; Tue, 23 Aug 2011 20:23:17 +0000 (UTC)
	(envelope-from lev@FreeBSD.org)
Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru
	[IPv6:2a01:4f8:131:60a2::2])
	by mx1.freebsd.org (Postfix) with ESMTP id E6BD38FC15
	for <freebsd-fs@FreeBSD.org>; Tue, 23 Aug 2011 20:23:16 +0000 (UTC)
Received: from lion.home.serebryakov.spb.ru (unknown
	[IPv6:2001:470:923f:1:b1b7:d4b2:b3b3:a68b])
	(Authenticated sender: lev@serebryakov.spb.ru)
	by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 97FEB4AC1C
	for <freebsd-fs@FreeBSD.org>; Wed, 24 Aug 2011 00:23:15 +0400 (MSD)
Date: Wed, 24 Aug 2011 00:23:12 +0400
From: Lev Serebryakov <lev@FreeBSD.org>
Organization: FreeBSD
X-Priority: 3 (Normal)
Message-ID: <12360197.20110824002312@serebryakov.spb.ru>
To: freebsd-fs@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1251
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: Is growfs(8) safe?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: lev@FreeBSD.org
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2011 20:23:17 -0000

Hello, Freebsd-fs.

 Is growfs(8) safe now? I remember, there were some problems with
non-zeroed data, but it seems to be fixed.

  But it HAS one bug for sure: "int p_size," which overflows on big
FSes. It is in sectors, and 32 bit signed, so max value is only
slightly less than 1Tb (!)

  I've fixed it (PR will be a bit later), but I'm not sure, is it
only bug in such important utility?

 Does somebody use it? Or everybody migrate to ZFS already?

--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>