Hi, after some unscheduled reboots (to put it lightly), I've got an interesting setup on my notebook's zfs partition: setup: simple zpool, no raid or mirror, a couple of zfs partitions, one zvol for swap. /foo is one such partition, /foo/bar the directory with the issue.
directly after the reboot happened: $ ls /foo/bar test.h $ ls -l /foo/bar Total 0 the file wasn't accessible with cat, etc. somewhat later (new data appeared on /foo, in /foo/baz): $ ls -l /foo/bar Total 3 -rw-r--r-- 1 user group 1400 Jul 6 02:14 test.h the content of test.h is the same as the content of /foo/baz/quux now, but the refcount is 1! $ chmod go-r /foo/baz/quux $ ls -l /foo/bar Total 3 -rw------- 1 user group 1400 Jul 6 02:14 test.h good, so at least it's no security concern. anyway, how do I get rid of test.h now without making quux unreadable? (the brute force approach would be a new partition, moving data over with copying - instead of moving - the troublesome file, just in case - not sure if zfs allows for links that cross zfs partitions and thus optimizes such moves, then zfs destroy data/test, but there might be a better way?) patrick mauritz This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
