From owner-freebsd-fs@FreeBSD.ORG Fri Jun 24 22:51:10 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2421D106566C; Fri, 24 Jun 2011 22:51:10 +0000 (UTC) (envelope-from mdf356@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id ABB3A8FC0A; Fri, 24 Jun 2011 22:51:09 +0000 (UTC) Received: by qwc9 with SMTP id 9so2171620qwc.13 for ; Fri, 24 Jun 2011 15:51:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xoojBqhilGK5L1Hus75v48OkrwKFZiWn2bhPt1cNq2g=; b=gt68RHQgih78fhtkSuZ6L5OZbUMHUWqfVrP/fRye2qvIPhRIppnwimBAlW/WXSfd4G R9eMrvSmbMpB40jZ6bY6xnds/qYEukapD4TMobE/2aIQoaLqJMd6i5Az85M4a2iHL+1/ DF/2GWKsmEvETgi1Zqz+VQVtA/2anHWcFh1FE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Qb1rbqKMqyRPFEApvY4M5tSygrunsmhWcgZaI5JvdKOnTPoDg9Am4q389HdgOlIBEn Sn00K+GIx4TSE1Ru+q3kiOzVJx1eenrztSPYKx6+vrYxfq1md8qZuAaXPJP8U+hcB0vW xFOvbMpVmeKMXQaIkn9xJsAfvIB5eIp+LpOL0= MIME-Version: 1.0 Received: by 10.229.215.6 with SMTP id hc6mr2932721qcb.93.1308954060099; Fri, 24 Jun 2011 15:21:00 -0700 (PDT) Sender: mdf356@gmail.com Received: by 10.229.241.197 with HTTP; Fri, 24 Jun 2011 15:21:00 -0700 (PDT) In-Reply-To: <4E04FC7F.6090801@FreeBSD.org> References: <20101201091203.GA3933@tops> <20110104175558.GR3140@deviant.kiev.zoral.com.ua> <20110120124108.GA32866@tops.skynet.lt> <4E027897.8080700@FreeBSD.org> <20110623064333.GA2823@tops> <20110623081140.GQ48734@deviant.kiev.zoral.com.ua> <4E03B8C4.6040800@FreeBSD.org> <20110623222630.GU48734@deviant.kiev.zoral.com.ua> <4E04FC7F.6090801@FreeBSD.org> Date: Fri, 24 Jun 2011 15:21:00 -0700 X-Google-Sender-Auth: rrG7Gd83jVcnAAvU_sOFjMNg4Pk Message-ID: From: mdf@FreeBSD.org To: Garance A Drosehn Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, Robert Watson Subject: Re: [rfc] 64-bit inode numbers X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2011 22:51:10 -0000 On Fri, Jun 24, 2011 at 2:07 PM, Garance A Drosehn wrote: > The AFS cell at RPI has approximately 40,000 AFS volumes, and each > volume should have it's own dev_t (IMO). > > Please realize that I do not mind if people felt that there was no > need to increase the size of dev_t at this time, and that we should > wait until we see more of a demand for increasing it. =A0But given the > project to increase the size of inode numbers, I thought this was a > good time to also ask about dev_t. =A0I ask about it every few years :-) I don't see why 32 bits are anywhere close to becoming tight to represent 40k unique values. Is there something wrong with how each new dev_t is computed, that runs out of space quicker than this implies? Thanks, matthew