Comment #6 on issue 1198 by darius.s...@rkt-online.com: gnt-backup does not
attach ext-based snapshot
https://code.google.com/p/ganeti/issues/detail?id=1198
In the meantime I did more tests, polished my provider log output again
(added date) and also added some log output lines inside the ganeti-os-defs
1.2.6 raw-image export script.
The export script now shows which device it gets from ganeti and writes it
to my providers log file.
On Dec 30th I wrote...
The provider logfile output (I have polished it in the meantime a little
bit) looks correct in both situations...
THIS WAS WRONG, SORRY. I did oversee a missing snapshot attach.
Here is the log output with Ganeti 2.15.2 "release" version:
--- attach --- Sat Dec 31 20:05:42 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
--- snapshot --- Sat Dec 31 20:05:43 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
snap_size: 10240
snap_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- attach --- Sat Dec 31 20:05:47 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
--- attach --- Sat Dec 31 20:05:47 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- start backup/export --- Sat Dec 31 20:05:49 CET 2016
/dev/rktstorage8/4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- end backup/export --- Sat Dec 31 20:08:41 CET 2016
--- attach --- Sat Dec 31 20:08:43 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- detach --- Sat Dec 31 20:08:43 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- remove --- Sat Dec 31 20:08:44 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
Here is the log output with Ganeti 2.15.2 from "stable-2.15" branch:
--- attach --- Sat Dec 31 19:58:02 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
--- snapshot --- Sat Dec 31 19:58:03 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
snap_size: 10240
snap_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- attach --- Sat Dec 31 19:58:07 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
--- start backup/export --- Sat Dec 31 19:58:09 CET 2016
/dev/rktstorage8/4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0
--- end backup/export --- Sat Dec 31 20:01:01 CET 2016
--- attach --- Sat Dec 31 20:01:03 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- detach --- Sat Dec 31 20:01:03 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
--- remove --- Sat Dec 31 20:01:03 CET 2016
disk_vg: rktstorage8
disk_vol: 4559a5b4-8bcb-4763-8033-d1acee641014.ext.disk0.snap
Now you can see that "stable-2.15" creates the snaphost, attaches the
origin but after that it does not even try to attach the snapshot it took
before.
It simply hands over the origin to the os backup script.
That's why the OS export script exports the wrong device (origin and not
snapshot).
I hope this helps.
In the next days I will try to bisect the first bad commit.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
