Issue 129 in zumastor: hourly snapshots are not happening

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

New issue report by hulugi:

Discription:

1. Create a single snapshotted volume on a real device

# pvcreate /dev/sda5
# vgcreate sysvg /dev/sda5
# lvcreate --name test --size 200M sysvg
# lvcreate --name test_snap --size 100M sysvg
# zumastor define volume zumatest /dev/sysvg/test /dev/sysvg/test_snap
--initialize
# mkfs.ext3 /dev/mapper/zumatest
# zumastor define master zumatest

2.Set up periodic snapshots
# zumastor define schedule zumatest --hourly 24

3.
# zumastor snapshot zumatest hourly

current output:
It takes the first snapshot hourly.0
after that it is not taking any further hourly snapshots

expected output:
it has to take snapshots hourly basis

Test setup:
processor: AMD Atholon 64 x2 Dual core processor 4800+
Host OS: CentOS 5.1, 2.6.18-53.1.14.el5xen
Guest OS: Ubuntu Gusty 7.10 (development branch)
2.6.22-10-Generic
Virtualization technology: Xen Full virtualization
zumastor: 2.6.22.18-zumastor-r1419

Issue attributes:
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #1 by pgquiles:
In step 3 you take an snapshot of an empty volume, which is OK. I guess
after that
you write data to the volume, how much data?

Explanation: your snapshot volume is half the data volume. That may
lead to problems
when the changes between the last snapshot and the next snapshot need
more space than
what's available in the snapshot store. If you've just written, say,
101MB of data,
that exceeds the capacity of the snapshot store, therefore it's
impossible to take a
new snapshot. As a rule of thumb, always make your snapshot store *at
least* the same
size your data store.

Another option is the cron job is not set executable. This bug was
present ~1 month
ago but I think it was fixed after chatting about this over IRC. Please
check the
permissions of /etc/cron.daily/zumastor , /etc/cron.weekly/zumastor and
/etc/cron.monthly/zumastor and make sure they are executable.

Please report your progress.

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #2 by hulugi:
* In step 3 i took an snapshot of an empty volume,
after that i wrote data to the volume of size 1MB

*and i checked the permissions of /etc/cron.hourly/zumastor the are not
made executable

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #3 by daniel.r.kegel:
try making it executable, then.

[sandy]

It is better to document it, until the issue gets fixed.

[Will Nowak]

This was fixed in debian packages in r1583 and higher. [Cronjobs are
installed with dh_installcron instead of from the tarball]
-Will

[Daniel Phillips]

sandy wrote:
> It is better to document it, until the issue gets fixed.

A fix is already checked in and part of release 0.8. Could you please try
0.8 to confirm that 1) the cron files are now installed as executable, and
2) this fixes the issue?

Regards,

Daniel

[sandy]

hi Dan,


* Yes i observed that in 0.8 release, after the installation of
zumastor,By default zumastor cron.script file permission are made
excecutable and it is fixed. and hourly snapshots are happenning

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #4 by daniel.r.kegel:
User reported that this is fixed in 0.8.

Issue attribute updates:
Status: Verified

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #5 by pgquiles:
This defect is still happening with zumastor 0.8.0r1659 on Ubuntu
Hardy. None of the
three cron jobs ( /etc/cron.hourly/zumastor , /etc/cron.daily/zumastor and
/etc/cron.weekly/zumastor ) are installed with execute permissions.

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #6 by daniel.r.kegel:
(No comment was entered for this change.)

Issue attribute updates:
Status: Accepted
Labels: Milestone-Release9

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #7 by daniel.r.kegel:
crontab scripts are considered configuration files, so an upgrade
won't touch them normally. If you do a fresh install of 0.8,
we expect it to work. Were you doing an update?

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #8 by pgquiles:
No, it was a clean install on just-installed Ubuntu Hardy servers

[codesite...@google.com]

Issue 129: hourly snapshots are not happening
http://code.google.com/p/zumastor/issues/detail?id=129

Comment #9 by daniel.r.kegel:
Which packages did you install, exactly?