From owner-freebsd-current@FreeBSD.ORG Thu Oct 6 09:26:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C7128106564A for ; Thu, 6 Oct 2011 09:26:54 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8431C8FC1B for ; Thu, 6 Oct 2011 09:26:54 +0000 (UTC) Received: by ywp17 with SMTP id 17so3025373ywp.13 for ; Thu, 06 Oct 2011 02:26:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xUHOHmRyz5idLXR7G2Gxv90FFake2PANd+9jHBQrka0=; b=BVUXE/ZJSijgXuqWqtWJWjjygx79PmAqTwEhO9Nbiy7KGs9vcUHEvz0LU6qSKe3sBx jHkUfc9UopEyji8qRvsyAHeZyxtYCwKJWSoxhNtUPgNb43I7qHvUH2nJ/5LF4s5aACnJ jFheF2uC0PohLgAAJ2p1UaOL5La9CUuqpAqpY= MIME-Version: 1.0 Received: by 10.236.190.200 with SMTP id e48mr2029922yhn.59.1317893213602; Thu, 06 Oct 2011 02:26:53 -0700 (PDT) Received: by 10.236.105.166 with HTTP; Thu, 6 Oct 2011 02:26:53 -0700 (PDT) In-Reply-To: References: <8B59D754-9062-4499-9873-7C2167622032@gromit.dlib.vt.edu> Date: Thu, 6 Oct 2011 10:26:53 +0100 Message-ID: From: krad To: Paul Mather X-Mailman-Approved-At: Thu, 06 Oct 2011 15:59:12 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Olivier Smedts , freebsd-current@freebsd.org Subject: Re: Strange ZFS filesystem corruption X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2011 09:26:55 -0000 On 6 October 2011 02:27, Paul Mather wrote: > On Oct 5, 2011, at 9:03 AM, krad wrote: > > > Have you dont the simple thing and checked to see if you have any weird > whitespace in the dir names. Try using bash tab completion for the dir name. > Also drop all non bash completion rules as these might be messing things up. > > > > I have seen odd characters in dirs cause much confusion in the past. > > > I don't believe that is the problem in this case. An "ls" will list the > file but "ls -l" reports "no such file or directory:" > > tape# ls > 05DLAAdmin 07DLAAdmin > tape# ls -l > ls: 05DLAAdmin: No such file or directory > total 3 > drwxrws--- 4 500 501 4 Oct 3 11:53 07DLAAdmin > tape# > > Plus, the "rm -rf" I tried (that failed) ought not to fall foul of such > weird whitespace problems. > > Cheers, > > Paul. > > > try a zfs mount -a, just incase some mounting has gone adrift. This certainly is strange