Thread: F15: need help packaging / VMware-Data-Recovery

Status: Beta

Brought to you by: andycking, dsouders, dtor, dynofu, and 3 others

open-vm-tools-devel

F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-03 18:49:01

Attachments: signature.asc

hi

i think i need help

below a src.rpm for Fedora 15 http://koji.fedoraproject.org/koji/buildinfo?buildID=276240
this is stripped down without all the gui/shared-folders-stuif and worked perfectly
some days ago

http://access.thelounge.net/harry/open-vm-tools-0.0.0.535097-26.fc15.20111203.rh.src.rpm

worked means:
* VDR backup successfull
* VDR probe-restore successfull
* VDR restore after destroy the guest with "rm -rf /" successfull
* VMware-HA sucessfull

well so for me the topic upgrade to Fedora 15 was done

yesterday i stared upgrade our build/admin-machine and the goldenmaster
all went fine, in the night from friday to saturday VMware-Data-Recovery
is scheduled for all machines - well the F15 guests failed

Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
Dec  3 16:55:38 master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
Dec  3 17:23:10 master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
Dec  3 17:53:30 master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.

what i really do not undertsand is why the hell this worked a few days before
like a charme and now no way and there is no option in VMware-Data-Recovery
to make only a crash-consistent backup (AFAIK)

if they vmware-tools are not installed this is used automatically
but this is no option because VMware-High-Ability needs the alive-signal
of the guest

hopefully anybody can figure out what here happens since F14 is EOL and
i guess there are many users needing this which do not want the oversized
official tools from VMware with all the useless binary-modules

yes, i do not build sepearted lib(kmod-packages because it is easier
and kernel-updates will first installed on the buildmachine, after a
reboot the vmware-tools rebuilt for this kernel and from this point
on the new kernel and modules are distributed to all other machines
which have only the interal repos active

-- 

Reindl Harald
the lounge interactive design GmbH
A-1060 Vienna, Hofmühlgasse 17
CTO / software-development / cms-solutions
p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40
icq: 154546673, http://www.thelounge.net/

http://www.thelounge.net/signature.asc.what.htm

Re: F15: need help packaging / VMware-Data-Recovery

From: Dmitry T. <dt...@vm...> - 2011-12-05 17:41:05

Hi Reindl,

On Saturday, December 03, 2011 07:48:51 PM Reindl Harald wrote:
> hi
> 
> i think i need help
> 
> below a src.rpm for Fedora 15
> http://koji.fedoraproject.org/koji/buildinfo?buildID=276240 this is
> stripped down without all the gui/shared-folders-stuif and worked perfectly
> some days ago
> 
> http://access.thelounge.net/harry/open-vm-tools-0.0.0.535097-26.fc15.2011120
> 3.rh.src.rpm
> 
> worked means:
> * VDR backup successfull
> * VDR probe-restore successfull
> * VDR restore after destroy the guest with "rm -rf /" successfull
> * VMware-HA sucessfull
> 
> well so for me the topic upgrade to Fedora 15 was done
> 
> yesterday i stared upgrade our build/admin-machine and the goldenmaster
> all went fine, in the night from friday to saturday VMware-Data-Recovery
> is scheduled for all machines - well the F15 guests failed
> 
> Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error freezing
> filesystems. Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup]
> Error freezing filesystems. Dec  3 16:55:38 master vmsvc[1183]: [ warning]
> [vmbackup] Error freezing filesystems. Dec  3 17:23:10 master vmsvc[1183]:
> [ warning] [vmbackup] Error freezing filesystems. Dec  3 17:53:30 master
> vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.

Please try enabling debug log in tools:

[logging]
log = true
vmbackup.level = debug
vmbackup.handler = vmx
vmvss.level = debug
vmvss.handler = vmx

Hopefully it will show what method is being used for syncing file systems and 
where exactly it fails.

Thanks,
Dmitry

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-05 18:00:13

Attachments: signature.asc

hi and thank you for your feedback

Am 05.12.2011 18:40, schrieb Dmitry Torokhov:
>> Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error freezing
>> filesystems. Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup]
>> Error freezing filesystems. Dec  3 16:55:38 master vmsvc[1183]: [ warning]
>> [vmbackup] Error freezing filesystems. Dec  3 17:23:10 master vmsvc[1183]:
>> [ warning] [vmbackup] Error freezing filesystems. Dec  3 17:53:30 master
>> vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
> 
> Please try enabling debug log in tools:
> 
> [logging]
> log = true
> vmbackup.level = debug
> vmbackup.handler = vmx
> vmvss.level = debug
> vmvss.handler = vmx
> 
> Hopefully it will show what method is being used for syncing file systems and 
> where exactly it fails.

in which config-file this should happen and is it enough to enable it or
has the debug-rpm built from rpmbuild to be installed before?

this i night i have to upgrade the last 3 machines and can play
around with this after that work, couurently my weekly woruaround
would look like disable HA partially, stop vmware-tools on all guests
and start the tools an full HA after vdr-backup

BTW:
is the "vmsync"-module really needed any longer?
i think the command/capability below exists since
some kernel versions

[root@srv-rhsoft:~]$ which fsfreeze
/sbin/fsfreeze
[root@srv-rhsoft:~]$ /sbin/fsfreeze --help
Usage: fsfreeze [options] <mount point>

Options:
 -h, --help          this help
 -f, --freeze        freeze the filesystem
 -u, --unfreeze      unfreeze the filesystem

For more information see fsfreeze(8).

Re: F15: need help packaging / VMware-Data-Recovery

From: Dmitry T. <dt...@vm...> - 2011-12-05 18:54:45

On Monday, December 05, 2011 07:00:04 PM Reindl Harald wrote:
> hi and thank you for your feedback
> 
> Am 05.12.2011 18:40, schrieb Dmitry Torokhov:
> >> Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error
> >> freezing
> >> filesystems. Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup]
> >> Error freezing filesystems. Dec  3 16:55:38 master vmsvc[1183]: [
> >> warning] [vmbackup] Error freezing filesystems. Dec  3 17:23:10
> >> master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
> >> Dec  3 17:53:30 master vmsvc[1183]: [ warning] [vmbackup] Error
> >> freezing filesystems.
> > 
> > Please try enabling debug log in tools:
> > 
> > [logging]
> > log = true
> > vmbackup.level = debug
> > vmbackup.handler = vmx
> > vmvss.level = debug
> > vmvss.handler = vmx
> > 
> > Hopefully it will show what method is being used for syncing file
> > systems and where exactly it fails.
> 
> in which config-file this should happen

/etc/vmware-tools/tools.conf

> and is it enough to enable it or
> has the debug-rpm built from rpmbuild to be installed before?

I do not think so.

> 
> this i night i have to upgrade the last 3 machines and can play
> around with this after that work, couurently my weekly woruaround
> would look like disable HA partially, stop vmware-tools on all guests
> and start the tools an full HA after vdr-backup
> 
> BTW:
> is the "vmsync"-module really needed any longer?
> i think the command/capability below exists since
> some kernel versions
> 
> [root@srv-rhsoft:~]$ which fsfreeze
> /sbin/fsfreeze
> [root@srv-rhsoft:~]$ /sbin/fsfreeze --help
> Usage: fsfreeze [options] <mount point>
> 
> Options:
>  -h, --help          this help
>  -f, --freeze        freeze the filesystem
>  -u, --unfreeze      unfreeze the filesystem
> 
> For more information see fsfreeze(8).

We are trying to use standard FIFREEZE ioctl and fall back to our vmsync 
driver of FIFREEZE is not available.

BTW, for production environments I'd recommend packaging 8.6.0 release, not 
the unstable release you are using.

Thanks,
Dmitry

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-06 11:21:17

Attachments: signature.asc


Am 05.12.2011 19:54, schrieb Dmitry Torokhov:
> On Monday, December 05, 2011 07:00:04 PM Reindl Harald wrote:
>> hi and thank you for your feedback
>>
>> Am 05.12.2011 18:40, schrieb Dmitry Torokhov:
>>>> Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error
>>>> freezing
>>>> filesystems. Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup]
>>>> Error freezing filesystems. Dec  3 16:55:38 master vmsvc[1183]: [
>>>> warning] [vmbackup] Error freezing filesystems. Dec  3 17:23:10
>>>> master vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
>>>> Dec  3 17:53:30 master vmsvc[1183]: [ warning] [vmbackup] Error
>>>> freezing filesystems.
>>>
>>> Please try enabling debug log in tools:
>>>
>>> [logging]
>>> log = true
>>> vmbackup.level = debug
>>> vmbackup.handler = vmx
>>> vmvss.level = debug
>>> vmvss.handler = vmx
>>>
>>> Hopefully it will show what method is being used for syncing file
>>> systems and where exactly it fails.
>>
>> in which config-file this should happen
> 
> /etc/vmware-tools/tools.conf

does not interest the vm-tools, with or without debug-rpm
and not with my changed version below nor exactly like
you suggested - there is nothing more information :-(

if there would be an option for the VDR to make only crash-consistent
backups this would help much because i need the vdr-backups usually
to restore whole machines if in the worst-case the san-storage dies

the data are backuped daily with rsync offsite, vdr once each week
crash-consistent works if i stop the vm-tools automatically but
then you have to take care disable automatic restart of crashed
virtual machines to avoid a hard reset
__________________

[root@buildserver:~]$ cat /var/log/messages | grep vmb
Dec  6 12:09:44 buildserver vmsvc[681]: [ warning] [vmbackup] Error freezing filesystems.

[root@buildserver:~]$ cat /etc/vmware-tools/tools.conf
[logging]
log = true
log.file = /var/log/vmtools.log

[vmbackup]
vmbackup.level = debug
vmbackup.handler = vmx
vmvss.level = debug
vmvss.handler = vmx
vss.log = true

[root@buildserver:~]$ stat /var/log/vmtools.log
  Datei: „/var/log/vmtools.log“
  Größe: 0              Blöcke: 0          EA Block: 4096   reguläre leere Datei
Gerät: 821h/2081d       Inode: 13          Verknüpfungen: 1
Zugriff: (0640/-rw-r-----)  Uid: (    0/    root)   Gid: (    0/    root)

[root@buildserver:~]$ cat /var/log/vmtools.log

Re: F15: need help packaging / VMware-Data-Recovery

From: Marcelo V. <mv...@vm...> - 2011-12-06 16:53:14

Hey Reindl,

On 12/06/2011 03:21 AM, Reindl Harald wrote:
> [root@buildserver:~]$ cat /etc/vmware-tools/tools.conf [logging] log =
> true log.file = /var/log/vmtools.log
> 
> [vmbackup] vmbackup.level = debug vmbackup.handler = vmx vmvss.level =
> debug vmvss.handler = vmx vss.log = true

Look at Dmitry's conf file again; it's different than yours.

> [root@buildserver:~]$ stat /var/log/vmtools.log

With Dmitry's config, the logs would show up in your VM's vmware.log (on the
ESX host), not anywhere inside the guest.

-- 
- Marcelo

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-06 16:55:31

Attachments: signature.asc


Am 06.12.2011 17:53, schrieb Marcelo Vanzin:
> Look at Dmitry's conf file again; it's different than yours.
> 
>> [root@buildserver:~]$ stat /var/log/vmtools.log
> 
> With Dmitry's config, the logs would show up in your VM's vmware.log (on the
> ESX host), not anywhere inside the guest.

oh - thank you, did not know this

i will give it another try asap
tomorrow not in the office - VMware SMB Roadshow in Vienna :-)

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-07 15:26:39

Attachments: signature.asc

hi

logoutput as requested at the end of this message
hope this helps

thank you!

Am 05.12.2011 18:40, schrieb Dmitry Torokhov:
>> Dec  3 16:24:59 master vmsvc[1183]: [ warning] [vmbackup] Error freezing
>> filesystems. Dec  3 16:25:27 master vmsvc[1183]: [ warning] [vmbackup]
>> Error freezing filesystems. Dec  3 16:55:38 master vmsvc[1183]: [ warning]
>> [vmbackup] Error freezing filesystems. Dec  3 17:23:10 master vmsvc[1183]:
>> [ warning] [vmbackup] Error freezing filesystems. Dec  3 17:53:30 master
>> vmsvc[1183]: [ warning] [vmbackup] Error freezing filesystems.
> 
> Please try enabling debug log in tools:
> 
> [logging]
> log = true
> vmbackup.level = debug
> vmbackup.handler = vmx
> vmvss.level = debug
> vmvss.handler = vmx
> 
> Hopefully it will show what method is being used for syncing file systems and 
> where exactly it fails.
> 
> Thanks,
> Dmitry

Dec 07 15:19:25.687: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver-flat.vmdk" : open successful (21) size
= 536870912, hd = 0. Type 3
Dec 07 15:19:25.693: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver-flat.vmdk" : closed.
Dec 07 15:19:25.709: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_1-flat.vmdk" : open successful (21)
size = 8589934592, hd = 0. Type 3
Dec 07 15:19:25.709: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_1-flat.vmdk" : closed.
Dec 07 15:19:25.716: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_2-flat.vmdk" : open successful (21)
size = 1073741824, hd = 0. Type 3
Dec 07 15:19:25.716: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_2-flat.vmdk" : closed.
Dec 07 15:19:25.721: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_3-flat.vmdk" : open successful (21)
size = 5368709120, hd = 0. Type 3
Dec 07 15:19:25.721: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_3-flat.vmdk" : closed.
Dec 07 15:19:25.729: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_4-flat.vmdk" : open successful (21)
size = 4294967296, hd = 0. Type 3
Dec 07 15:19:25.729: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_4-flat.vmdk" : closed.
Dec 07 15:19:25.735: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_5-flat.vmdk" : open successful (21)
size = 12884901888, hd = 0. Type 3
Dec 07 15:19:25.735: vmx| DISKLIB-VMFS  :
"/vmfs/volumes/4c5ff85a-c4e18c48-6b43-78e7d1e8c6aa/buildserver_1/buildserver_5-flat.vmdk" : closed.
Dec 07 15:19:25.736: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupStart
Dec 07 15:19:25.737: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Using quiesceApps = 1, quiesceFS = 1,
allowHWProvider = 1,execScripts = 1, scriptArg = , timeout = 0
Dec 07 15:19:25.737: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Quiescing volumes: (null)
Dec 07 15:19:25.737: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackup_SendEvent
Dec 07 15:19:25.738: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupStartScripts
Dec 07 15:19:25.738: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Trying to run scripts from
/etc/vmware-tools/backupScripts.d
Dec 07 15:19:26.739: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupAsyncCallback
Dec 07 15:19:26.740: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] VmBackupAsyncCallback: checking VmBackupOnFreeze
Dec 07 15:19:26.740: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Async request 'VmBackupOnFreeze' completed
Dec 07 15:19:26.740: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupEnableSync
Dec 07 15:19:26.740: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupSyncDriverStart
Dec 07 15:19:26.757: vcpu-1| Guest: [ warning] [vmsvc:vmbackup] Error freezing filesystems.
Dec 07 15:19:26.758: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackup_SendEvent
Dec 07 15:19:26.758: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupStartScripts
Dec 07 15:19:26.758: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Trying to run scripts from
/etc/vmware-tools/backupScripts.d
Dec 07 15:19:27.760: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupAsyncCallback
Dec 07 15:19:27.760: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] VmBackupAsyncCallback: checking VmBackupOnFreezeFail
Dec 07 15:19:27.760: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] Async request 'VmBackupOnFreezeFail' completed
Dec 07 15:19:27.761: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackupFinalize
Dec 07 15:19:27.761: vcpu-1| Guest: [   debug] [vmsvc:vmbackup] *** VmBackup_SendEvent

Re: F15: need help packaging / VMware-Data-Recovery

From: Marcelo V. <mv...@vm...> - 2011-12-07 22:43:21

Hi Reindl,

On 12/07/2011 07:26 AM, Reindl Harald wrote:
>> [logging] log = true vmbackup.level = debug vmbackup.handler = vmx 
>> vmvss.level = debug vmvss.handler = vmx

Sorry but I'll have to ask you to change the log config again, since the
config above unfortunately doesn't enable logging for the library that
actually does the freezing.

Use this instead:
[logging]
log = true
vmsvc.level = debug
vmsvc.handler = vmx

That will generate a few more logs than the previous settings. Feel free to
send the new vmware.log directly to my e-mail if you think it's too large.

-- 
- Marcelo

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-07 23:26:18

Attachments: signature.asc vmware.log.tar.gz

Am 07.12.2011 23:43, schrieb Marcelo Vanzin:
> Sorry but I'll have to ask you to change the log config again, since the
> config above unfortunately doesn't enable logging for the library that
> actually does the freezing.
> 
> Use this instead:
> [logging]
> log = true
> vmsvc.level = debug
> vmsvc.handler = vmx
> 
> 
> That will generate a few more logs than the previous settings. Feel free to
> send the new vmware.log directly to my e-mail if you think it's too large.

no problem, our VPN is working from vCenter back to my home-machine :-)
compressed log attached, contains all logs from a new start of the VM
until freeze of filesystem / online-backup failed

i think these two lines are the relevant
ioctl failed because ressource busy

Dec 07 23:05:17.551: vcpu-0| Guest: [   debug] [vmsvc:vmsvc] SyncDriver: ioctl failed: 16 (Das Gerät oder die
Ressource ist belegt)
Dec 07 23:05:17.553: vcpu-0| Guest: [ warning] [vmsvc:vmbackup] Error freezing filesystems.
____________________________

wouldn't it be a good idea to switch this from ioctl to fsfreeze or
look inside the guest-tools if fsfreeze is supported and use it in
such cases, RHEL5 is missing it, RHEL6 supports it and fedora as
many other distributions do also because they switched to recent
kernels long ago

> [root@buildserver:~]$ fsfreeze --help
> Usage: fsfreeze [options] <mount point>
>
> Options:
> -h, --help          this help
> -f, --freeze        freeze the filesystem
> -u, --unfreeze      unfreeze the filesystem
>
> For more information see fsfreeze(8).
> [root@buildserver:~]$ fsfreeze -f /
> [root@buildserver:~]$ fsfreeze -u /

       -f, --freeze
              This option requests the specified a filesystem to be frozen from new modifications.  When this is
              selected, all ongoing transactions in the filesystem are allowed to  complete,  new  write  system
              calls  are  halted,  other calls which modify the filesystem are halted, and all dirty data, meta‐
              data, and log information are written to disk.  Any process attempting  to  write  to  the  frozen
              filesystem will block waiting for the filesystem to be unfrozen.

              Note  that  even  after freezing, the on-disk filesystem can contain information on files that are
              still in the process of unlinking.  These files will not  be  unlinked  until  the  filesystem  is
              unfrozen or a clean mount of the snapshot is complete.

Re: F15: need help packaging / VMware-Data-Recovery

From: Marcelo V. <mv...@vm...> - 2011-12-08 00:00:36

On 12/07/2011 03:26 PM, Reindl Harald wrote:
> Dec 07 23:05:17.551: vcpu-0| Guest: [   debug] [vmsvc:vmsvc] SyncDriver:
> ioctl failed: 16 (Das Gerät oder die Ressource ist belegt)

Hmmm... Dmitry just showed me the new kernel sources and this interface seems
to have changed since I first looked at it. Could you try to apply this patch
and see if it helps:

diff --git a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
index 7dfae42..7d84f98 100644
--- a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
+++ b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
@@ -191,9 +191,13 @@ LinuxDriver_Freeze(const char *paths,
           * supported on the device, we get EOPNOTSUPP. Ignore the latter,
           * since freezing does not make sense for all fs types, and some
           * Linux fs drivers may not have been hooked up in the running kernel.
+          *
+          * The kernel may also return EBUSY if the superblock is already
+          * frozen, which can happen if, for example, multiple mount points
+          * exist.
           */
          close(fd);
-         if (errno != EOPNOTSUPP) {
+         if (errno != EOPNOTSUPP && errno != EBUSY) {
             Debug(LGPFX "ioctl failed: %d (%s)\n", errno, strerror(errno));
             err = first ? SD_UNAVAILABLE : SD_ERROR;
             break;


> wouldn't it be a good idea to switch this from ioctl to fsfreeze or look
> inside the guest-tools if fsfreeze is supported and use it in such cases

fsfreeze most probably just uses the same ioctl interface we're using
directly, so there wouldn't be any difference in functionality, only more
complicated code.

-- 
- Marcelo

Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-08 00:15:07

Attachments: signature.asc

Am 08.12.2011 01:00, schrieb Marcelo Vanzin:
> On 12/07/2011 03:26 PM, Reindl Harald wrote:
>> Dec 07 23:05:17.551: vcpu-0| Guest: [   debug] [vmsvc:vmsvc] SyncDriver:
>> ioctl failed: 16 (Das Gerät oder die Ressource ist belegt)
> 
> Hmmm... Dmitry just showed me the new kernel sources and this interface seems
> to have changed since I first looked at it. Could you try to apply this patch
> and see if it helps:
> 
> diff --git a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
> b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
> index 7dfae42..7d84f98 100644
> --- a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
> +++ b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
> @@ -191,9 +191,13 @@ LinuxDriver_Freeze(const char *paths,
>            * supported on the device, we get EOPNOTSUPP. Ignore the latter,
>            * since freezing does not make sense for all fs types, and some
>            * Linux fs drivers may not have been hooked up in the running kernel.
> +          *
> +          * The kernel may also return EBUSY if the superblock is already
> +          * frozen, which can happen if, for example, multiple mount points
> +          * exist.
>            */
>           close(fd);
> -         if (errno != EOPNOTSUPP) {
> +         if (errno != EOPNOTSUPP && errno != EBUSY) {
>              Debug(LGPFX "ioctl failed: %d (%s)\n", errno, strerror(errno));
>              err = first ? SD_UNAVAILABLE : SD_ERROR;
>              break;

rpmbuild does not like this patch, see below

my one for the fedora-version looks a little different
and was done with "diff -uNr", help appreciated

>[builduser@buildserver:/rpmbuild/SPECS]$ cat /rpmbuild/SOURCES/open-vm-tools-2.6.41.patch
>--- open-vm-tools-original/modules/linux/shared/compat_netdevice.h      2011-10-27 20:57:11.000000000 +0200
>+++ open-vm-tools-patched/modules/linux/shared/compat_netdevice.h       2011-11-23 16:57:55.814275389 +0100
>@@ -184,7 +184,7 @@
>  * so let's add back ones we care about.
>  */
> #if !defined(HAVE_NET_DEVICE_OPS) && \
>-         LINUX_VERSION_CODE >= KERNEL_VERSION(3, 0, 0)
>+         LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 41)
> #   define HAVE_NET_DEVICE_OPS 1
> #endif
_____________________

[builduser@buildserver:/rpmbuild/SPECS]$ rpmbuild -bb vmware-tools.spec
Ausführung(%prep): /bin/sh -e /var/tmp/rpm-tmp.QMx1dr
+ umask 022
+ cd /home/builduser/rpmbuild/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /home/builduser/rpmbuild/BUILD
+ rm -rf open-vm-tools-2011.11.20-535097
+ /usr/bin/gzip -dc /home/builduser/rpmbuild/SOURCES/open-vm-tools-2011.11.20-535097.tar.gz
+ /bin/tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd open-vm-tools-2011.11.20-535097
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ echo 'Patch #1 (open-vm-tools-2.6.41.patch):'
Patch #1 (open-vm-tools-2.6.41.patch):
+ /bin/cat /home/builduser/rpmbuild/SOURCES/open-vm-tools-2.6.41.patch
+ /usr/bin/patch -s -p1 --fuzz=0
+ echo 'Patch #2 (open-vm-tools-vsync.patch):'
Patch #2 (open-vm-tools-vsync.patch):
+ /bin/cat /home/builduser/rpmbuild/SOURCES/open-vm-tools-vsync.patch
+ /usr/bin/patch -s -p1 --fuzz=0
The text leading up to this was:
--------------------------
|diff --git a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
|b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
|index 7dfae42..7d84f98 100644
|--- a/open-vm-tools/lib/syncDriver/syncDriverLinux.c
|+++ b/open-vm-tools/lib/syncDriver/syncDriverLinux.c
--------------------------
File to patch:

Re: F15: need help packaging / VMware-Data-Recovery

From: Marcelo V. <mv...@vm...> - 2011-12-08 00:19:49

On 12/07/2011 04:14 PM, Reindl Harald wrote:
> Patch #2 (open-vm-tools-vsync.patch): + /bin/cat
> /home/builduser/rpmbuild/SOURCES/open-vm-tools-vsync.patch + /usr/bin/patch
> -s -p1 --fuzz=0

Perhaps you should use -p0 instead? I don't know, I don't have your rpmbuild
setup here so I can't suggest many things. It's a one-line change, so worst
case you can manually create the patch against your tree.

-- 
- Marcelo

Re: F15: need help packaging / VMware-Data-Recovery

From: Dmitry T. <dt...@vm...> - 2011-12-08 00:24:00

On Wednesday, December 07, 2011 04:19:42 PM Marcelo Vanzin wrote:
> On 12/07/2011 04:14 PM, Reindl Harald wrote:
> > Patch #2 (open-vm-tools-vsync.patch): + /bin/cat
> > /home/builduser/rpmbuild/SOURCES/open-vm-tools-vsync.patch +
> > /usr/bin/patch -s -p1 --fuzz=0
> 
> Perhaps you should use -p0 instead? I don't know, I don't have your rpmbuild
> setup here so I can't suggest many things. It's a one-line change, so worst
> case you can manually create the patch against your tree.

I think it actually needs -p2 to strip "a/open-vm-tools/" prefix from the 
paths.

Thanks,
Dmitry

SOLVED (open-vm-tools): Re: F15: need help packaging / VMware-Data-Recovery

From: Reindl H. <h.r...@th...> - 2011-12-08 00:50:09

Attachments: signature.asc

open-vm-tools for recent Fedora 15 kernels and VMware-HA/dataRecovery
see below

Am 08.12.2011 01:19, schrieb Marcelo Vanzin:
> On 12/07/2011 04:14 PM, Reindl Harald wrote:
>> Patch #2 (open-vm-tools-vsync.patch): + /bin/cat
>> /home/builduser/rpmbuild/SOURCES/open-vm-tools-vsync.patch + /usr/bin/patch
>> -s -p1 --fuzz=0
> 
> Perhaps you should use -p0 instead? I don't know, I don't have your rpmbuild
> setup here so I can't suggest many things. It's a one-line change, so worst
> case you can manually create the patch against your tree.

HALLELUJAH IT WORKS
vnd-backup of the buildserver is currently at 45%

this is my src.rpm for fedora 15 >= 2.6.41
cross-post on fedora-devel/fedora-users/rpmfusion list

hopefully that it helps people standing in the rain since rpmfusion is missing updates
http://access.thelounge.net/harry/open-vm-tools-0.0.0.535097-27.fc15.20111208.rh.src.rpm

this package is intentent to be used on servers and builds no gui-tools/dependencies
and no shared-folders modules to get rid of some unwanted packages, it also removes
VMXNET2 since VMXNET3 is included in the upstream kernel

it does not use any kmod-tools, so you need one buildmachine with disabled HA to rebuild the
package after update/reboot this machine and distribute it with the matching kernel from your
own repo to the other machines where you should be aware to boot with the old kernel as long
HA is active with automatic restart of frozen guests!
____________________________________

> The kernel may also return EBUSY if the superblock is already frozen, which
> can happen if, for example, multiple mount points exist

makes sense and matches to my most-hated change nobody cares
wondering why it worked in my first test, but who cares now
https://bugzilla.redhat.com/show_bug.cgi?id=730138
____________________________________

i do not know much about diff/patch but some changes at the begin
made the difference, removing the first two lines und the subfolder
"a/" and "b/" in the first lines

that is why i prfer the "snapshot" open-vm-tools since fedora tends to
use recent software and the frozen versions are mostly problematic
to compile

> --- open-vm-tools/lib/syncDriver/syncDriverLinux.c
> +++ open-vm-tools/lib/syncDriver/syncDriverLinux.c
> @@ -191,9 +191,13 @@ LinuxDriver_Freeze(const char *paths,
>           * supported on the device, we get EOPNOTSUPP. Ignore the latter,
>           * since freezing does not make sense for all fs types, and some
>           * Linux fs drivers may not have been hooked up in the running kernel.
>+          *
>+          * The kernel may also return EBUSY if the superblock is already
>+          * frozen, which can happen if, for example, multiple mount points
>+          * exist.
>           */
>          close(fd);
>-         if (errno != EOPNOTSUPP) {
>+         if (errno != EOPNOTSUPP && errno != EBUSY) {
>             Debug(LGPFX "ioctl failed: %d (%s)\n", errno, strerror(errno));
>             err = first ? SD_UNAVAILABLE : SD_ERROR;
>             break;