Date: Wed, 5 Oct 2011 21:27:37 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: krad <kraduk@gmail.com> Cc: Olivier Smedts <olivier@gid0.org>, freebsd-current@freebsd.org Subject: Re: Strange ZFS filesystem corruption Message-ID: <FC06F6E8-43E5-404D-AC00-342F9AEB4CD6@gromit.dlib.vt.edu> In-Reply-To: <CALfReycJ6VkKPNJ_C65CPQzPnEeozjEAOxzf6bcGdtk2-HuPyQ@mail.gmail.com> References: <8B59D754-9062-4499-9873-7C2167622032@gromit.dlib.vt.edu> <CABzXLYOsXWxR8u2RvuVekQ4%2BgwPQKT6C1dSasQoAUdGY0VBMjQ@mail.gmail.com> <CALfReycJ6VkKPNJ_C65CPQzPnEeozjEAOxzf6bcGdtk2-HuPyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >=20 > 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#=20 Plus, the "rm -rf" I tried (that failed) ought not to fall foul of such = weird whitespace problems. Cheers, Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FC06F6E8-43E5-404D-AC00-342F9AEB4CD6>