From owner-cvs-src@FreeBSD.ORG Thu Sep 8 07:45:52 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2167716A41F for ; Thu, 8 Sep 2005 07:45:52 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 47F6543D49 for ; Thu, 8 Sep 2005 07:45:51 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 99878 invoked from network); 8 Sep 2005 07:45:50 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 8 Sep 2005 07:45:50 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 8 Sep 2005 02:45:47 -0500 (CDT) From: Mike Silbersack To: Dmitry Pryanishnikov In-Reply-To: <20050908094705.R19771@atlantis.atlantis.dp.ua> Message-ID: <20050908024022.G28140@odysseus.silby.com> References: <20050908094705.R19771@atlantis.atlantis.dp.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/fs/msdosfs msdosfs_denode.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Sep 2005 07:45:52 -0000 On Thu, 8 Sep 2005, Dmitry Pryanishnikov wrote: > I've thought about it too ;) > > Actually, to trigger this error one should have little more than 4Gb device, > but carefully placed directory on it ;) If we have 2 files, which directory > entries begin at byte offsets from the start of the media with identical > low-order 32 bits; e.g., 64-bit offsets > > 0x0000000000001000 and > 0x0000000100001000 Hm, maybe it wouldn't be too difficult to create, then. There is an option to have compressed filesystems, so if one wrote a huge filesystem with files that all contained zeros, perhaps it would compress well enough. If you just started creating a lot of equally sized files containing zero as their content, maybe it could be done via a script. Yeah, you could just call truncate in some sort of shell script loop until you have enough files, then go back and try reading file "000001", and that should cause the panic, right? Mike "Silby" Silbersack