I was hoping someone might be able to help me discover why I'm not
getting auto snapshots of my data pool, please?
I've a system installed with build 127, and upgraded to 128a.
Two pools:
ca...@miles:~$ zpool list
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
rpool 99.5G 9.42G 90.1G 9% 1.00x ONLINE -
tank 1.71T 770M 1.71T 0% 1.00x ONLINE -
I've asked time-slider to take snapshots of all filesystems in both pools:
ca...@miles:~$ zfs get com.sun:auto-snapshot rpool tank
NAME PROPERTY VALUE SOURCE
rpool com.sun:auto-snapshot true local
tank com.sun:auto-snapshot true local
(and these settings are inherited in all child fs)
The services appear to be OK:
ca...@miles:~$ svcs -xv
ca...@miles:~$ svcs time-slider auto-snapshot
STATE STIME FMRI
online 0:00:05 svc:/system/filesystem/zfs/auto-snapshot:hourly
online 0:00:05 svc:/system/filesystem/zfs/auto-snapshot:monthly
online 0:00:05 svc:/system/filesystem/zfs/auto-snapshot:frequent
online 0:00:05 svc:/system/filesystem/zfs/auto-snapshot:weekly
online 0:00:05 svc:/system/filesystem/zfs/auto-snapshot:daily
online 10:24:11 svc:/application/time-slider:default
as is zpool status (although I'm still on pool version 19 for both pools).
Yet I'm only seeing automatic snapshots for rpool, and all its child fs.
There are no auto snapshots at all occurring for tank:
ca...@miles:~$ zfs list -r -d 1 -t snapshot rpool
NAME USED AVAIL REFER
MOUNTPOINT
rp...@oneoff 0 - 83K -
rp...@zfs-auto-snap:monthly-2009-12-10-22:16 0 - 83K -
rp...@zfs-auto-snap:hourly-2009-12-10-23:16 20K - 83K -
rp...@zfs-auto-snap:hourly-2009-12-11-21:16 0 - 83K -
rp...@zfs-auto-snap:daily-2009-12-11-22:16 0 - 83K -
rp...@zfs-auto-snap:frequent-2009-12-11-22:46 0 - 83K -
ca...@miles:~$ zfs list -r -d 1 -t snapshot tank
NAME USED AVAIL REFER MOUNTPOINT
t...@oneoff 17K - 21K -
t...@my-snapshot-2009-12-10_23h47:37 17K - 21K -
If I enable time-slider debugging:
ca...@miles:~$ svccfg -s time-slider setprop daemon/verbose = true
and then look at the log, I see that it sees tank, but then seems to
ignore it:
[ Dec 11 23:16:26 Rereading configuration. ]
[ Dec 11 23:16:26 Executing refresh method (:kill). ]
Warning level value is: 80%
Critical level value is: 90%
Emergency level value is: 95%
ZPool name: rpool
Health: ONLINE
Used: 13709Mb
Available: 86586Mb
Capacity: 13.669468062%
ZPool name: tank
Health: ONLINE
Used: 3025Mb
Available: 1762990Mb
Capacity: 0.171290828481%
Last monthly snapshot was: rp...@zfs-auto-snap:monthly-2009-12-10-22:16
Recalculating monthly schedule
Recalculating weekly schedule
Last daily snapshot was: rp...@zfs-auto-snap:daily-2009-12-11-22:16
Recalculating daily schedule
Last hourly snapshot was: rp...@zfs-auto-snap:hourly-2009-12-11-23:16
Recalculating hourly schedule
Last frequent snapshot was: rp...@zfs-auto-snap:frequent-2009-12-11-23:01
Recalculating frequent schedule
Waiting until 1260574266
Waiting 880 seconds
I did think perhaps that it had created them, and they'd subsequently
been removed as "zero sized", but having created data in them, and
waited, with still no snapshots, that's clearly not the case.
What am I missing here, please? Presumably it's something obvious...
It's as though it doesn't know how to bootstrap the first set of
auto-snapshots, from which it can then work out the subsequent
schedules. Do I need to do something to kick that off?
thanks much indeed.
cheers,
calum.
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
