<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title></title><style type="text/css">.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style></head><body><blockquote class="felamimail-body-blockquote"></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">samuli wrote: </span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"><span style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">Can you try to set storage.owner-uid and storage.owner-gid to </span><br style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><span style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">libvirt-qemu? To do that you have to stop volume.</span><br style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><blockquote class="felamimail-body-blockquote"><span style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"></span></blockquote></blockquote><p>hi samuli, hi all </p><p><br></p><p>I tried setting storage.owner-uid and storage.owner-gid to </p><p>libvirt-qemu, as suggested, but with the same effect,</p><p>during livemigration the ownership of the imagefile changes from libvirt-qemu/kvm to root/root</p><p><br></p><p>root@pong[/5]:~ # gluster volume info glfs_atom01</p><p> </p><p>Volume Name: glfs_atom01</p><p>Type: Replicate</p><p>Volume ID: f28f0f62-37b3-4b10-8e86-9b373f4c0e75</p><p>Status: Started</p><p>Number of Bricks: 1 x 2 = 2</p><p>Transport-type: tcp</p><p>Bricks:</p><p>Brick1: 172.24.1.11:/ecopool/fs_atom01</p><p>Brick2: 172.24.1.13:/ecopool/fs_atom01</p><p>Options Reconfigured:</p><p>storage.owner-gid: 104</p><p>storage.owner-uid: 107</p><p>network.remote-dio: enable</p><p><br></p><p>this is tree -pfungiA <path to where my images live> : atom01 is running</p><p><br></p><p>[-rw------- libvirt- kvm ] /srv/vms/mnt_atom01/atom01.img</p><p>[drwxr-xr-x libvirt- kvm ] /srv/vms/mnt_atom02</p><p>[-rw------- root root ] /srv/vms/mnt_atom02/atom02.img</p><p>[drwxr-xr-x libvirt- kvm ] /srv/vms/mnt_atom03</p><p><br></p><p>Now I migrate through "VirtualMachineManager" and watching tree</p><p>I see the permission changing to:</p><p><br></p><p>[drwxr-xr-x libvirt- kvm ] /srv/vms/mnt_atom01</p><p>[-rw------- root root ] /srv/vms/mnt_atom01/atom01.img</p><p>[drwxr-xr-x libvirt- kvm ] /srv/vms/mnt_atom02</p><p>[-rw------- root root ] /srv/vms/mnt_atom02/atom02.img</p><p><br></p><p>From inside the atom01 (the VM) the filesystem becomes readonly.</p><p>But in contrast to</p><a href="http://epboven.home.xs4all.nl/gluster-migrate.html" target="_blank" style="font-family: verdana; font-size: 13px; background-color: rgb(255, 255, 255);">http://epboven.home.xs4all.nl/gluster-migrate.html</a><br style="font-family: verdana; font-size: 13px; background-color: rgb(255, 255, 255);"><p>I can still read all file, can checksum them, just no write access</p><p>from outside the image file behaves as Paul described,</p><p>as long as the machine is running I can't read the file</p><p><br></p><p><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # virsh list</span></p><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;"> Id Name State</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">----------------------------------------------------</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;"> 6 atom01 running</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><font face="tahoma, arial, helvetica, sans-serif"><br></font><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # l /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">-rw------- 1 root root 10G Jan 24 10:20 /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # file /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">/srv/vms/mnt_atom01/atom01.img: writable, regular file, no read permission</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # md5sum /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">md5sum: /srv/vms/mnt_atom01/atom01.img: Permission denied</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # virsh destroy atom01</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">Domain atom01 destroyed</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><font face="tahoma, arial, helvetica, sans-serif"><br></font><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # l /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">-rw------- 1 root root 10G Jan 24 10:20 /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # file /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">/srv/vms/mnt_atom01/atom01.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 16777165 sectors; partition 2: ID=0xf, starthead 254, startsector 16777228, 1677718 sectors, code offset 0x63</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">root@pong[/5]:~ # md5sum /srv/vms/mnt_atom01/atom01.img</span><br><blockquote class="felamimail-body-blockquote"><blockquote class="felamimail-body-blockquote"></blockquote></blockquote><span style="font-family: tahoma, arial, helvetica, sans-serif;">9d048558deb46fef7b24e8895711c554 /srv/vms/mnt_atom01/atom01.img</span><br><font face="tahoma, arial, helvetica, sans-serif">root@pong[/5]:~ # </font><blockquote class="felamimail-body-blockquote" style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"></blockquote><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><br></p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">But interestingly the source of the migration can access the file after migration completed</p><p style="font-family: tahoma, arial, helvetica, sans-serif;">like so: start atom01 on host "ping", migrate it to "pong"</p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><br></p><p>root@pong[/8]:~ # file /srv/vms/mnt_atom01/atom01.img</p><p>/srv/vms/mnt_atom01/atom01.img: writable, regular file, no read permission </p><p>root@ping[/5]:~ # file /srv/vms/mnt_atom01/atom01.img</p><p>/srv/vms/mnt_atom01/atom01.img: x86 boot sector; partition 1: ID=0x83, starthead 1, startsector 63, 16777165 sectors; partition 2: ID=0xf, starthead 254, startsector 16777228, 1677718 sectors, code offset 0x63</p><div><br></div><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">100% reproducible </p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><br></p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">Regards</p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;"><br></p><p style="font-family: tahoma, arial, helvetica, sans-serif; font-size: 13px;">Bernhard</p><style type="text/css">.felamimail-body-blockquote {margin: 5px 10px 0 3px;padding-left: 10px;border-left: 2px solid #000088;} </style></body></html>