search for: snap_hour

...usedbychildren 0 - daten/backups usedbyrefreservation 0 - daten/backups at zfs-auto-snap_hourly-2009-12-20-16_00 used 228M - daten/backups at zfs-auto-snap_hourly-2009-12-20-17_00 used 150K - daten/b...

...not, I discovered recently that time-sliderd was doing just a ton of "close" requests. I disabled time-sliderd while trying to solve my performance problem. I was also getting these error messages in the time-sliderd log file: Warning: Cleanup failed to destroy: rpool/ROOT at zfs-auto-snap_hourly-2010-11-10-15h01 Details: [''/usr/bin/pfexec'', ''/usr/sbin/zfs'', ''destroy'', ''-d'', ''rpool/ROOT at zfs-auto-snap_hourly-2010-11-10-15h01''] failed with exit code 1 cannot destroy ''rpool/ROOT at zfs-auto...

...all. The shadow:snapprefix, etc seems to be the way to do it, but I am unable to get it to work. When I setup the prefix, etc, I get know previous versions at all. My setup in Smb.conf is below, and my directories are named as follows: shadow:snapprefix = ^\(zfs-auto-snap_dai\)\{0,1\}\(zfs-auto-snap_hour\)\{0,1\}$ shadow:delimiter = ly- shadow:format = ly-%Y-%m-%d-%H%M Directories : zfs-auto-snap_daily-2018-01-01-1235 zfs-auto-snap_daily-2018-03-15-1135 zfs-auto-snap_daily-2018-03-29-1135 zfs-auto-snap_hourly-2018-04-03-1817 zfs-auto-snap_hourly-2018-04-04-0817 zfs-auto-snap_weekly-2018-01-17-1...

...of the same problem... Unfortunately, now I have a filesystem where "zfs receive" was interrupted, and I can''t destroy the filesystem or the snapshot of the filesystem on the receiving side. sudo zfs destroy -R tank/Downloads cannot destroy ''tank/Downloads at zfs-auto-snap_hourly-2012-08-31-17h54'': dataset already exists sudo zfs destroy -R tank/Downloads at zfs-auto-snap_hourly-2012-08-31-17h54 cannot destroy snapshot tank/Downloads at zfs-auto-snap_hourly-2012-08-31-17h54: snapshot is cloned sudo zfs list -t all | grep Downloads tank/Downloads tank/Downloads...

.../. \ /data/snapshots/hourly.0/folder/mail/ Where the local destination /data/snapshots is an NFS volume mounted with the flags (rw,noatime,addr=192.168.1.XX) and the source is a symlink to a zfs snapshot - that looks like this: /var/backups/mail -> /tank/mail/.zfs/snapshot/zfs-auto-snap_hourly-2015-01-07-1417 as far as I can tell, both systems work with UTF8 just fine (source is Ubuntu 14.04 and target is Debian Lenny) Now there seems to be a problem while gathering or transferring the file list, as rsync tries to create files/folders that share a part with real files on the source,...

...wrote: > >> Where the local destination /data/snapshots is an NFS volume mounted with the flags >> (rw,noatime,addr=192.168.1.XX) >> and the source is a symlink to a zfs snapshot - that looks like this: >> /var/backups/mail -> /tank/mail/.zfs/snapshot/zfs-auto-snap_hourly-2015-01-07-1417 > > Why not skip the NFS part and run rsync to the destination over the > network? Rsync is written to minimize network traffic at the cost of > local IO, and if you're doing NFS then that "local IO" is really also > network traffic. You also elimina...

...Jan 2015, Lenz Weber wrote: > Where the local destination /data/snapshots is an NFS volume mounted with the flags > (rw,noatime,addr=192.168.1.XX) > and the source is a symlink to a zfs snapshot - that looks like this: > /var/backups/mail -> /tank/mail/.zfs/snapshot/zfs-auto-snap_hourly-2015-01-07-1417 Why not skip the NFS part and run rsync to the destination over the network? Rsync is written to minimize network traffic at the cost of local IO, and if you're doing NFS then that "local IO" is really also network traffic. You also eliminate one potential source o...