Bug 173718 - [zfs] phantom directory in zraid2 pool
Summary: [zfs] phantom directory in zraid2 pool
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-19 13:30 UTC by Brian Gold
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Gold 2012-11-19 13:30:00 UTC
I am running a zraid2 pool (v28) on 6 sata drives which are passed through a Dell SAS 6/iR running in TI mode for pass-through. This FreeBSD server functions as backup storage for our site. All of our servers are rsynced over to this server each night for backup.

Recently, I've noticed that I will get messages like the following in my rsync log:
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"

I then run a simple ls on the directory: "ls /backup/ldap1/etc" and the pki subdirectory shows up just fine.

Fix: 

Eventually, I decide to manually delete the entire "/backup/ldap1" directory and all of its contents. Everything deletes just fine, except for the directories that were erroring in my rsync logs. I then re-run my rsync job and those directories are populated without issue.

Now however, I am getting different directories erroring during the nightly rsync:
"/backup/ldap1/var/lib/yum/yumdb/i/8b1b1eb729e16ac4c3d877718de59d12b2ee7c2a-iso-codes-3.16-2.el6-noarch" failed: No such file or directory (2)"

And from my daily security email output:
Checking setuid files and devices:
find: /backup/ldap1/var/lib/yum/yumdb/c/1e68056c53f1cd6b5ddf78fc18e8fcada22d89d9-cdparanoia-libs-10.2-5.1.el6-x86_64/from_repo_revision: No such file or directory
find: /backup/ldap1/var/lib/yum/yumdb/i/8b1b1eb729e16ac4c3d877718de59d12b2ee7c2a-iso-codes-3.16-2.el6-noarch: No such file or directory
How-To-Repeat: I have no idea how to cause this issue on another system unfortunately. I did however locate a few postings on the forums of other users who experienced similar issues.
http://lists.freebsd.org/pipermail/freebsd-current/2011-October/027902.html
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-12-03 05:05:14 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:37 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped