From owner-cvs-src@FreeBSD.ORG Thu Sep 8 08:37:02 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 654F616A41F; Thu, 8 Sep 2005 08:37:02 +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 7D98A43D48; Thu, 8 Sep 2005 08:37:01 +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 j888ah3c065324; Thu, 8 Sep 2005 11:36:43 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Thu, 8 Sep 2005 11:36:43 +0300 (EEST) From: Dmitry Pryanishnikov To: Mike Silbersack In-Reply-To: <20050908024022.G28140@odysseus.silby.com> Message-ID: <20050908112746.K43691@atlantis.atlantis.dp.ua> References: <20050908094705.R19771@atlantis.atlantis.dp.ua> <20050908024022.G28140@odysseus.silby.com> 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 08:37:02 -0000 On Thu, 8 Sep 2005, Mike Silbersack wrote: >> 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. BTW, how can one work with compressed filesystem? > > 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? Our task is slightly different: not our files should start at magic offset, but their _directory entries_. I think this task is achievable by creating new FAT32 filesystem, then (in strict order) a directory, a large (approx. 4Gb) file in it, a second directory, a file in it, then lookup first file. In order to get a panic whe just have to tune size of the large file. If I have enough time I'll try to prepare such a regression test. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE