Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Nov 2012 09:36:33 -0500
From:      "Brian Gold" <bgold@simons-rock.edu>
To:        <freebsd-questions@freebsd.org>
Subject:   odd phantom directory
Message-ID:  <06e901cdc407$c69ee650$53dcb2f0$@simons-rock.edu>

next in thread | raw e-mail | index | archive | help
Hi all,

 

I ran into a rather odd issue this morning with my FreeBSD 9.0-Release
system running ZFS v28. This system serves as an RSYNC host which all of our
other systems back up to each night. Last night, I started getting the
following error:

 

file has vanished: "/backup/ldap1/etc/pki"

Now, usually when I get a file has vanished error during an RSYNC run, it
indicates that the source file/directory on the system that is sending the
rsync backup has been deleted or moved before rsync got a chance to actually
send it. That doesn't appear to be the case here. "/backup/ldap1/etc/pki" is
the destination directory on my Freebsd/ZFS server. I take a look in
"/backup/ldap1/etc" on my Freebsd server and the "pki" subdirectory is no
longer listed.

 

Ok, so I run "mkdir /backup/ldap1/etc/pki" and get the following error:
"mkdir: /backup/ldap1/etc/pki: File exists". Odd

Just to double check, I run "ls -la /backup/ldap1/etc/pki" and get the
following: "ls: /backup/ldap1/etc/pki: No such file or directory"

Alright, how about a simple touch? "touch: /backup/ldap1/etc/pki: No such
file or directory"

Fine. Maybe there is something funky about the "/backup/ldap1/etc" directory
that is preventing me from doing any of this. "mkdir
/backup/ldap1/etc/pki2". That works just fine.

What the heck?

 

 

Looking at the output of my daily security run, I see the following:

Checking setuid files and devices:

find: /backup/ldap1/etc/fonts/conf.avail: No such file or directory

find: /backup/ldap1/etc/fonts/conf.d/30-metric-aliases.conf: No such file or
directory

find: /backup/ldap1/etc/pki: No such file or directory

 

So, it looks like there are a few files/directories in /backup/ldap1/etc
that were affected.

 

Looking through dmesg and /var/log/messages, I don't see anything out of the
ordinary. 

 

I'm running a zpool scrub now just to be on the safe side, but I haven't
seen any checksum or other errors so far.

 

Any thoughts as to what might be causing this?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?06e901cdc407$c69ee650$53dcb2f0$>