From owner-freebsd-stable Tue Dec 21 9: 5:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 13E6E15382 for ; Tue, 21 Dec 1999 09:05:43 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA35453; Tue, 21 Dec 1999 09:05:39 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Dec 1999 09:05:39 -0800 (PST) From: Doug White To: Michael Robinson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) In-Reply-To: <199912211316.VAA50647@netrinsics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Michael Robinson wrote: > 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. find -print0 | xargs -0 is your friend. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message