search

junneyang / zumastor

Automatically exported from code.google.com/p/zumastor
0 stars 1 forks source link

hourly snapshots are not happening #129

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 

 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

Original issue reported on code.google.com by hul...@gmail.com on 8 May 2008 at 8:18

GoogleCodeExporter commented 9 years ago 
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.

Original comment by pgqui...@gmail.com on 8 May 2008 at 10:36

GoogleCodeExporter commented 9 years ago 
* 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

Original comment by hul...@gmail.com on 8 May 2008 at 2:10

GoogleCodeExporter commented 9 years ago 
try making it executable, then.

Original comment by daniel.r...@gmail.com on 8 May 2008 at 2:55

GoogleCodeExporter commented 9 years ago 
User reported that this is fixed in 0.8.

Original comment by daniel.r...@gmail.com on 14 May 2008 at 6:52

GoogleCodeExporter commented 9 years ago 
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.

Original comment by pgqui...@gmail.com on 18 May 2008 at 9:50

GoogleCodeExporter commented 9 years ago

Original comment by daniel.r...@gmail.com on 19 May 2008 at 12:15

GoogleCodeExporter commented 9 years ago 
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?

Original comment by daniel.r...@gmail.com on 21 May 2008 at 7:11

GoogleCodeExporter commented 9 years ago 
No, it was a clean install on just-installed Ubuntu Hardy servers

Original comment by pgqui...@gmail.com on 21 May 2008 at 9:26

GoogleCodeExporter commented 9 years ago 
Which packages did you install, exactly?

Original comment by daniel.r...@gmail.com on 21 May 2008 at 9:28

GoogleCodeExporter commented 9 years ago 
This does not happen to us since 0.8. We may need more information about the 
issue.
Un-target from Release9.

Original comment by jiahotc...@gmail.com on 5 Jun 2008 at 5:06

GoogleCodeExporter commented 9 years ago 
This is still working on fresh installs of 0.9 and higher. Marking invalid 
until we 
get more information.

Original comment by williama...@gmail.com on 12 Jun 2008 at 4:32