From owner-freebsd-stable Tue Dec 21 3:16:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 222E0152A7 for ; Tue, 21 Dec 1999 03:16:21 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (gj-14-180.bta.net.cn [202.106.14.180]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id SAA23382 for ; Tue, 21 Dec 1999 18:07:59 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id SAA50337; Tue, 21 Dec 1999 18:02:12 +0800 (CST) (envelope-from robinson) Date: Tue, 21 Dec 1999 18:02:12 +0800 (CST) From: Michael Robinson Message-Id: <199912211002.SAA50337@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Extremely bizarre filename behavior (3.3-RELEASE) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an image repository indexed by md5 checksum. The repository has about eleven thousand images, and about two dozen directory entries like this: ---------------- # ls -li cb/d3 total 60 468593 -rwxr-xr-x 1 nobody staff 30063 Dec 17 18:54 cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cb/d3/cbd3b669fd20b2164b4391b053ed02e8.JPG ls: cb/d3/cbd3b669fd20b2164b4391b053ed02e8.JPG: No such file or directory ---------------- In other words, there is a directory entry, but the file can't be accessed directly. Then things get wierd: ---------------- # cd cb/d3 # touch * # ls -l total 60 -rwxr-xr-x 1 nobody staff 30063 Dec 21 17:49 cbd3b669fd20b2164b4391b053ed02e8.JPG ---------------- So, the directory entry is attached to a real live inode, whose modification time can be updated with "touch *". But then it gets really, really wierd: ---------------- # touch cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cbd3b669fd20b2164b4391b053ed02e8.JPG cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cbd3b669fd20b2164b4391b053ed02e8.JPG cbd3b669fd20b2164b4391b053ed02e8.JPG # ls -li total 60 468650 -rw-r--r-- 1 root staff 0 Dec 21 17:50 cbd3b669fd20b2164b4391b053ed02e8.JPG 468593 -rwxr-xr-x 1 nobody staff 30063 Dec 21 17:49 cbd3b669fd20b2164b4391b053ed02e8.JPG ---------------- This filesystem passes fsck without a peep. Is it possible that the vast number of long, random filenames is causing lossage in the filename hashing? The system is 3.3-RELEASE. I'm going to upgrade to 3.4-RELEASE tonight to see if the problems persist. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message