[Users] [User] why VM image owner change to root after stop the vm

[Martin Kletzander]

On 07/26/2012 02:30 PM, Dan Kenigsberg wrote:
> On Thu, Jul 26, 2012 at 11:05:21AM +0800, T-Sinjon wrote:
>> maybe it's a libvirt problem  , since my nodes have used oVirt Node Hypervisor 2.2.2-2.2.fc16
>>
>> engine:
>> libvirt-0.9.11.4-3.fc17.x86_64
> This one is unused.
> 
>>
>> node:
>> libvirt-0.9.6-4.fc16.x86_64
>>
>> storage:
>> No local fs, I have two Domain , one is using NFS fs, the other is GlusterFS mount by NFS.
>> Both have the problem
>>
>> [root at ovirt-node-sun-1 ~]# strace -p 1209 -e chown -ff
>> Process 1209 attached with 11 threads - interrupt to quit
>>
>> After start vm:
>> [pid  1518] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19068, si_status=0, si_utime=1, si_stime=1} (Child exited) ---
>> [pid  1518] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19069, si_status=0, si_utime=1, si_stime=1} (Child exited) ---
>> [pid  1518] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19071, si_status=0, si_utime=1, si_stime=1} (Child exited) ---
>> [pid  1518] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19072, si_status=0, si_utime=1, si_stime=1} (Child exited) ---
>> [pid  1518] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19074, si_status=0, si_utime=1, si_stime=0} (Child exited) ---
>> [pid  1209] --- {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=19080, si_status=0, si_utime=0, si_stime=0} (Child exited) ---
>> [pid  1518] chown("/rhev/data-center/3bdc6f14-bb92-4b0e-8db2-d0ba4c34f61d/b5078b10-a044-42c5-b270-8b81cd51ce35/images/979c2849-2587-4015-bad5-53159a11b6ed/38648b73-b0d4-4f2a-9f46-5b20613abb7a", 107, 107) = 0  
>>
>> After stop vm:
>> [pid  1209] chown("/rhev/data-center/3bdc6f14-bb92-4b0e-8db2-d0ba4c34f61d/b5078b10-a044-42c5-b270-8b81cd51ce35/images/979c2849-2587-4015-bad5-53159a11b6ed/38648b73-b0d4-4f2a-9f46-5b20613abb7a", 0, 0) = 0
> 
> 
> Why are you are teasing us? ;-) who was pid 1209, vdsm or libvirtd?
> 

=)

Unfortunately, you might be right, Dan. I think maybe it is libvirt and
it is hitting a bug, but the bug I know about does this only with
dynamic_ownership=1 (that's why I asked at first).

To be sure, let's wait till we know who was 1518. Until then I'll try to
investigate ;)

Martin