From owner-freebsd-arch@FreeBSD.ORG Sat Sep 3 16:51:56 2005 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C71C216A41F for ; Sat, 3 Sep 2005 16:51:56 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F32BB43D45 for ; Sat, 3 Sep 2005 16:51:55 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from smtp.atlantis.dp.ua (smtp.atlantis.dp.ua [193.108.46.231]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id j83Gpj0w013870; Sat, 3 Sep 2005 19:51:45 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Sat, 3 Sep 2005 19:51:45 +0300 (EEST) From: Dmitry Pryanishnikov To: Bruce Evans In-Reply-To: <20050903190632.S1788@atlantis.atlantis.dp.ua> Message-ID: <20050903194401.E1788@atlantis.atlantis.dp.ua> References: <20050901183311.D62325@atlantis.atlantis.dp.ua> <20050902205456.S2885@delplex.bde.org> <20050903190632.S1788@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-arch@FreeBSD.org Subject: Re: kern/85503: panic: wrong dirclust using msdosfs in RELENG_6 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Sep 2005 16:51:56 -0000 On Sat, 3 Sep 2005, Dmitry Pryanishnikov wrote: >> I think I said that the inode number in msdosfs should be the cluster >> number of the first cluster in the file. This would be broken by >> variable-sized clusters (unlikely, and even less useful) or new file >> types like symlinks (useful and not so unlikely -- FreeBSD could add >> them as an extension). > > Yes, I agree with this. While this fs has being called FAT32, > it's cluster number will fit in 32-bit word. Ups, how about empty files? They haven't any allocated clusters, have they? So, alas, we can't go this route. > I think interoperability with other OSes is also important, and if, e.g. > Microsoft will invent FAT64, we will return to this topic ;) Or, more realistically, NTFS will support >4Gfiles/fs... I won't even be surprised if they already do. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE