On 11/19/12 1:14 PM, Jim Klimov wrote:
On 2012-11-19 20:58, Mark Shellenbaum wrote:
There is probably nothing wrong with the snapshots. This is a bug in
ZFS diff. The ZPL parent pointer is only guaranteed to be correct for
directory objects. What you probably have is a file that was hard
linked multiple times and the parent pointer (i.e. directory) was
recycled and is now a file
Interesting... do the ZPL files in ZFS keep pointers to parents?
The parent pointer for hard linked files is always set to the last link
to be created.
$ mkdir dir.1
$ mkdir dir.2
$ touch dir.1/a
$ ln dir.1/a dir.2/a.linked
$ rm -rf dir.2
Now the parent pointer for "a" will reference a removed directory.
The parent pointer is a single 64 bit quantity that can't track all the
possible parents a hard linked file could have.
Now when the original dir.2 object number is recycled you could have a
situation where the parent pointer for points to a non-directory.
The ZPL never uses the parent pointer internally. It is only used by
zfs diff and other utility code to translate object numbers to full
pathnames. The ZPL has always set the parent pointer, but it is more
for debugging purposes.
How in the COW transactiveness could the parent directory be
removed, and not the pointer to it from the files inside it?
Is this possible in current ZFS, or could this be a leftover
in the pool from its history with older releases?
Thanks,
//Jim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
