From owner-freebsd-stable Tue Dec 21 5:18:23 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 102FE14F70 for ; Tue, 21 Dec 1999 05:18:19 -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 VAA07716 for ; Tue, 21 Dec 1999 21:18:00 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id VAA50647 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 21:16:14 +0800 (CST) (envelope-from robinson) Date: Tue, 21 Dec 1999 21:16:14 +0800 (CST) From: Michael Robinson Message-Id: <199912211316.VAA50647@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) In-Reply-To: <199912211002.SAA50337@netrinsics.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >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. Ok, I'm an idiot. Terminating spaces were leaking in from Windows users through Samba. It never occurred to me that sending filenames through a pipe from "find" to "xargs" (how I discovered the problem) will strip whitespace from filenames. Sorry. Older and wiser, now. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message