muh6mm3d / vmfs

Automatically exported from code.google.com/p/vmfs
0 stars 0 forks source link

snapshot ghosts #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
the dir commands show zero sized snapshot files for guests that don't
currently have snapshots.  On the ESX console, the files do not show.

Original issue reported on code.google.com by cwe...@gmail.com on 12 May 2009 at 4:17

GoogleCodeExporter commented 9 years ago
Please add more details (command's output, debug log).

Original comment by fluidops...@gmail.com on 20 May 2009 at 4:21

GoogleCodeExporter commented 9 years ago
does this mean you are unable to reproduce the behavior?  

I seem to be having trouble getting a complete log, when I use "2>&1 > 
debug.log" I
still get some messages on the console.  what's the java way of doing this?

Original comment by cwe...@gmail.com on 20 May 2009 at 1:05

GoogleCodeExporter commented 9 years ago
We didn't see this issue yet. Any idea how this behavior can be provoked? Does 
it
show this effect on all of your FS, or only sporadically?

Logging: wrong order, 'java ... >debug.log 2>&1' should work, or try 'java ... 
>>
debug.log 2>> debug.log'

Original comment by fluidops...@gmail.com on 21 May 2009 at 2:10

GoogleCodeExporter commented 9 years ago
yes, all my fs's and all the guests.  Seems simply make a snapshot then remove 
it. 
Or even touch a file then delete it on the ESX host.

not sure if it matters, these are VMFS on iscsi and the VMFS's are active while
reading them.  I'll try to get the debug log again tomorrow

Original comment by cwe...@gmail.com on 21 May 2009 at 2:16

GoogleCodeExporter commented 9 years ago
log attached, the dir on the ESX host looks like this:
drwxr-xr-x    1 root     root          840 May 21 10:00 phd
-rw-------    1 root     root     542234338 Apr 26 10:43 prod1-d559aa35.vmss
-rw-------    1 root     root     536870912 Apr 26 10:43 prod1-d559aa35.vswp
-rw-------    1 root     root     27169013760 May 21 10:40 prod1-flat.vmdk
-rw-------    1 root     root         8684 Apr 26 10:43 prod1.nvram
-rw-------    1 root     root          497 May 16 10:26 prod1.vmdk
-rw-------    1 root     root          463 May 16 10:26 prod1.vmsd
-rwxr-xr-x    1 root     root         2022 May 16 10:26 prod1.vmx
-rw-------    1 root     root          260 May 11 16:16 prod1.vmxf
-rw-r--r--    1 root     root        26963 Apr 18 14:42 vmware-10.log
-rw-r--r--    1 root     root        91715 Apr 26 08:37 vmware-11.log
-rw-r--r--    1 root     root        99654 Mar  7 08:13 vmware-6.log
-rw-r--r--    1 root     root       225160 Apr 18 11:28 vmware-7.log
-rw-r--r--    1 root     root        33925 Apr 18 11:35 vmware-8.log
-rw-r--r--    1 root     root        30289 Apr 18 14:37 vmware-9.log
-rw-r--r--    1 root     root       184654 May 16 10:27 vmware.log

I'm not sure why there's a prod8 snapshot file in prod1's dir either, I don't 
think a
prod8 disk was ever in prod1's dir before

Original comment by cwe...@gmail.com on 21 May 2009 at 3:45

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by fluidops...@gmail.com on 26 Jan 2010 at 7:17