Hi guys. I've been having a problem with Timeslider (well, since about OpenSolaris Nevada 130 something). Having done a complete reinstall of Solaris 11.1, and brought it up to the current SRU (SRU11.1.12.5.0), I'm still having issues.
What I'm finding is that timeslider fills up past the autodelete level (75%), and generally gets bogged down, and fills up to 100% eventually without corrective action. And the svc:/application/time-slider/plugin:zfs-send service (Time Slider Plugin Framework), usually gets put into maintenance mode by time-slider. What I've found is that time-slider puts zfs holds (why?) on zfs snapshots, and the snapshots never get deleted. I can unblock it with something like: fixtimeslider.sh : ------------------------ #!/bin/sh svcadm disable -t time-slider for f in `zfs list -H -t snapshot -o name`; do \ zfs release -r org.opensolaris:time-slider-plugin:zfs-send $f; done svcadm clear svc:/application/time-slider/plugin:zfs-send svcadm enable time-slider ------------------------ I ran this over the weekend, and was able to reduce the zpool utilisation down from 95% used down to 60%. However, zfs held snapshots have started appearing again: root@marvin:~# for f in `zfs list -t snapshot -o name`; do zfs holds $f; done 2>&1 | grep "zfs-send" rpool@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:50 2013 rpool/ROOT/SRU11.1.11.4.0/var@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:49 2013 rpool/ROOT/SRU11.1.12.5.0/var@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:50 2013 rpool/ROOT/s11.1ga/var@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:48 2013 rpool/VARSHARE@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:49 2013 rpool/VMs@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:49 2013 rpool/download@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:47 2013 rpool/export/home/crispi@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:47 2013 rpool/export/users@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:48 2013 rpool/ftp@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:46 2013 rpool/incoming@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:46 2013 rpool/isos@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:47 2013 rpool/squid@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:45 2013 rpool/www@zfs-auto-snap_hourly-2013-11-11-00h46 org.opensolaris:time-slider-plugin:zfs-send Mon Nov 11 00:46:45 2013 So - Why is this happening? And what is the long term fix? - surely zfs/timeslider should be more reliable than this? -- Regards, Chris _______________________________________________ msosug mailing list [email protected] http://mexico.purplecow.org/m/listinfo/msosug
