On Apr 16, 2010, at 5:33 PM, Edward Ned Harvey wrote: >> From: Richard Elling [mailto:richard.ell...@gmail.com] >> >> There are some interesting design challenges here. For the general >> case, you >> can't rely on the snapshot name to be in time order, so you need to >> sort by the >> mtime of the destination. > > Actually ... > > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-01-00-00-00/ > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-02-00-00-00/ > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-03-00-00-00/ > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-04-00-00-00/ > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-05-00-00-00/ > drwxr-xr-x 16 root root 20 Mar 29 12:07 daily-2010-04-06-00-00-00/ > > Um ... All the same time. > Even if I "stat" those directories ... > Access: Modify: and Change: are all useless...
which is why you need to stat the destination :-) > > How in the heck can you identify when a snapshot was taken, if you're not > relying on the name of the snapshot? "zfs list -t snapshot" lists in time order. > > >> It would be cool to only list files which are different. > > Know of any way to do that? cmp But since the world has moved onto time machine, time slider, and whatever Windows users use, is this tool relegated to the CLI dinosaurs? ;-) -- richard ZFS storage and performance consulting at http://www.RichardElling.com ZFS training on deduplication, NexentaStor, and NAS performance Las Vegas, April 29-30, 2010 http://nexenta-vegas.eventbrite.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
