82ff4b2f80
bug fix (wrong recursive filesystem list expansion)
...
in case of empty filesystem list going for recursive snapshot all
filesystems have been processed
2013-01-14 10:56:49 +01:00
9bf3d5b017
Revert "bug fix (wrong recursive filesystem list expansion)"
...
This reverts commit d6c05fb8f4
.
2013-01-14 10:37:32 +01:00
ba171cc032
Revert "bug fix (snapshot list created for destroy in case of incremental send through replication)"
...
This reverts commit 8b155cf4da
.
2013-01-14 10:37:13 +01:00
8b155cf4da
bug fix (snapshot list created for destroy in case of incremental send through replication)
2013-01-14 10:35:32 +01:00
d6c05fb8f4
bug fix (wrong recursive filesystem list expansion)
...
in case of empty filesystem list going for recursive snapshot all
filesystems have been processed
2013-01-14 10:35:03 +01:00
4bbfa476b1
general cleanup, quotations updates etc
2013-01-09 14:17:49 -06:00
583fc20e28
error return codes renumbering, parameter checking for --send
2013-01-03 14:49:05 -06:00
2d789bdf1d
detection of system (Linux/Darwin). proper detection of mounted snapshots prior to umount.
...
detection of system applies for local and remote operations. should run
on linux and macosx with no modifications in the code.
2013-01-03 14:49:05 -06:00
8aaf5f904b
issue #8 should be solved by this patch
...
all filesystems with snapdir=visible and canmount=on are traversed for
snapshots going to be removed and umount -f is called.
on linux, on /proc/mounts such mounted snapshots are visible (not
listed with 'mount'), but under macosx no proc exists, 'mount' again
does not list them so umount -f is called with no mercy for all
specific combination of fs and snapname (but should not cause any
problems).
there is no specific logic to utilize /proc/mount on linux, same
approach is taken.
2012-12-28 14:14:23 -06:00
6f91e10033
mktemp on macosx uses some .Xs by default, which is not the case on linux
2012-12-28 14:14:23 -06:00
1099c622cb
comments update
2012-12-27 20:58:22 -06:00
70632c00b7
going back to standard /bin/sh (bash 3.x on macosx)
2012-12-27 20:58:22 -06:00
90825db245
README updates
2012-12-27 20:58:22 -06:00
676ded6217
fix for filesystem expansion when using '//'
2012-12-27 20:58:22 -06:00
4d20aa4c79
Zevo support.
2012-12-27 20:58:10 -06:00
cc9f1802ed
Fix pool exclusions.
...
Use $ZPOOL_STATUS instead of $ZFS_STATUS for pool exclusions.
A mistaken variable name made the pool exclusion logic a no-op and
broke the --skip-scrub switch.
Also correct a trivial comment typo.
upstream/1.0.8
2012-01-21 16:32:30 -06:00
d77af5a902
Update the README file to be more descriptive.
2012-01-10 08:10:05 -06:00
b5bf1149ca
Merge pull request #2 from ulope/master
...
Fixed --prefix and --sep regexes
upstream/1.0.7
2011-12-28 10:06:04 -08:00
5fc395c2bb
Fixed --prefix and --sep regexes
...
Fixes : #1
2011-12-28 17:06:34 +01:00
d99147db7a
Set keep=8 in the weekly cron job.
...
A default of keep=8 for weekly snapshot is more useful than keep=4,
which is no more protective than the default daily schedule.
2011-12-21 20:29:27 -06:00
c8507a0da9
Change objects to datasets in help and comments.
...
In the usage synopsis and program comments, change "objects" to
"datasets" for consistency with upstream ZFS terminology.
2011-12-18 07:34:40 -06:00
74359e51a7
Fix the hourly-daily transposition in the Makefile.
...
The hourly cron job was installed to cron.daily, and the daily cron
job was installed to cron.hourly, which caused incorrect scheduling.
upstream/1.0.6
2011-11-28 00:07:30 -06:00
afdae86271
Remove redundant lines in the cron.d file.
2011-11-28 00:05:43 -06:00
4b7609791b
Split the cron file for anacron compatibilty.
...
Split the cron file so that the hourly, daily, weekly, and monthly
zfs automatic snapshots still happen even if the system is offline
temporarily during the scheduled event, such as during a reboot.
On Debian systems, if anacron is installed, then it is used to run
the /etc/cron.{hourly,daily,weekly,monthly} directories, but not
the /etc/cron.d directory. This means that /etc/cron.d jobs are not
run if the system is offline when crond would usually invoke them.
upstream/1.0.5
2011-11-25 14:26:08 -06:00
5ce7a23384
Implement the --event option for :auto-snap-desc.
...
Set the com.sun:auto-snap-desc property on each snapshot to an
arbitrary value. On Solaris, this property is set to the dash
character by default -- which is convention for NULL -- but it
can contain an FMRI status comment or other user data.
upstream/1.0.4
2011-11-23 10:44:32 -06:00
2e26499f6a
Rebase exit codes to above 127.
...
Most standard shell utilities return errors less than 128. Rebase the
exit codes of this script to reduce the liklihood of overlap.
2011-11-23 10:03:56 -06:00
f7ceb28963
Implement --prefix parameter checking.
...
Also add -p to the getopt list of short options.
2011-11-23 10:00:24 -06:00
4c14da4130
Consistently quote literal strings.
...
Apply some syntax hygiene. Quoting everything is a safe habit because
unquoted things can have subtle side-effects.
2011-11-22 23:36:51 -06:00
249e6a4cb3
Fold the main loops into a do_snapshots function.
...
The two primary `for` loops were identical except for the '-r' flag.
2011-11-22 23:27:24 -06:00
a0a43a42af
Invert the --skip-scrub test.
...
The $opt_skip_scrub option was tested incorrectly, which caused
the --skip-scrub option to operate opposite intent.
2011-11-22 22:09:23 -06:00
d8b1730015
Add an explicit exit 0
to the end of the script.
...
The implicit return is "$?", which can be set non-zero by
an earlier command.
upstream/1.0.3
2011-11-21 21:44:37 -06:00
adebbd6fee
Add -q to the getopt list of short options.
...
This corresponds to the --quiet option.
upstream/1.0.2
2011-11-21 21:40:04 -06:00
5bdcaad4bf
Expand the options variable in the cron part file.
...
Cron doesn't do variable substitution and zfs-auto-snapshot doesn't
load options from its environment.
upstream/1.0.1
2011-11-21 20:40:24 -06:00
875b55c967
Repository creation.
2011-11-21 19:47:20 -06:00