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.

Attachment: vmware.log.tar.gz
Description: GNU Zip compressed data

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
open-vm-tools-devel mailing list
open-vm-tools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel

Reply via email to