To locate and remove Ghost & corrupted log files files in VMFS Datstore

Related to vSphere 5.5[upgraded from 4.1] ..recently we did in place vmfs upgrade & there was firmware upgrade done @san level as well
now from last few days...we are getting  few errors

"ON-DISK ERROR: FB inconsistency found: (8010,0) allocated in bitmap, but never used"

and due to this we are unable to delete few orphaned vmdk from data store, we can see same folder there on multiple lun.

Can we remove such file using any valid method wich can be action with no interruption to running services ?
also would like to confirm for below given quires...

>What is ghost file and corrupted log  files in vmfs data store? and what could be reason behind it ?
>Can we avoid such file creation ?
>Will that ghost or corrupted file cause datastore corruption or any other major impact ?
>is Orphaned vmdk related  to such ghost or corrupted files ?
>How can we remove such files easily with no service interruption or how to fix this issue on permanent basis ?
>what could be reason behind such ghost or corrupted files ? is in place upgrade reason behind it ?
In Place upgrade is not recommended by VMware ?
LVL 1
patronAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

patronAuthor Commented:
we are unable to remove such log file or vmdk ,because file allocation table or root dir seems to be corrupted ? and VMFS unable to locate all blocks and entries for the files to be deleted.
What could be reason behind it ?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You can use RV Tools, to check for orphaned files and delete them, if not in use.

http://www.robware.net/
0
patronAuthor Commented:
I am able to locate orphaned files ,but when trying to delete no luck ?

is it related to ghsot file and what could be done to get this fixed ?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you cannot delete them check they are not in use.

what ghost files do you have ?
0
patronAuthor Commented:
yes, they r not in use,but yet not able to delete n files are like log files n vmdk etc not in use??
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
log files from what ?

screenshots please
0
patronAuthor Commented:
normally we should have 10 folder on data store  as there r 10 vms created on datastore ,but here we found 12 folders n under those 2 extra folder we found few vmdk, vmk or logs which r created for any virtual machine , so when we try to delete them it seem files r locked ..unable to delete ??
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
you need to check if they are in use, does RV Tools suggest they are orphaned.
0
patronAuthor Commented:
Strange that file/vmdk identified by rvtool n powergui as orphaned are like...

>few of them are of cource not in use n dirty/duplicate file to be removed
>but few of them are attached to running vms as second hard drives ..but why those are consider as orphaned ?

can in place or scratch upgrade cause a datastore to be corrupted ?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
well if they are connected and in use by a VM, they are not orphaned, and in use.

can in place or scratch upgrade cause a datastore to be corrupted ?

anything is possible, but we've not seen it.
0
patronAuthor Commented:
okay, further i need to use voma to look for more detail ..

Can we use voma on running infra..i mean will there be any impact or prerequisites if required ?

i need to check vmfs consistency if my datsore is okay   using voma tool.

please confirm if we have other  better way to check if lun is okay with no issues n impcat ?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, you can use VOMA to check for VMFS corruption.
0
patronAuthor Commented:
got your point ,Thanks

Can we use voma for running infra if vms are running on datasore with prod infra ?

or if any better tool to locate n fix the problem @datasore level in case there is any corruption or crash due to orphaned ghost files ??

i mean m looking for healthcheck for my data store, further orphaned i can remove accordingly

can we get orphaned due to vaai feature enabled in vmfs 5 ..causes svmotion delayed due to drivers or etc not compatible ?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you have a concern about the corruption of a datastore - what do you think ? would be wise about the VMs currently hosted on A CORRUPT DATASTORE ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
patronAuthor Commented:
yes ,its big question here, so need your expert advise on this, as yet there are 30+ vms running on same dataore ,but we have have orphaned disk/files for 3-4 vms on same datastore [which was recently prepared from scratch with vmfs5]

Now if we look for below given logs...
FS3_ADDR_INVALID  

Below errors were seen after running VMFS check using VOMA tool by someone else.
Phase 5: Checking resource reference counts.
ON-DISK ERROR: FB inconsistency found: (8010,0) allocated in bitmap, but never used
ON-DISK ERROR: FB inconsistency found: (8021,27) allocated in bitmap, but never used


and logs like
Mapping for file abcd.vmdk (34376533 bytes in size):
[           0:    12582912] --> [VMFS -- LVID:56bacca5-61a9bfe9-c083-5cf3fc5b9b14/56bacca5-51e8abc6-4675-5cf3fc5b9b14/1:( 1184909754368 -->  1184922337280)]
[    12582912:     8388608] --> [VMFS Z- LVID:56bacca5-61a9bfe9-c083-5cf3fc5b9b14/56bacca5-51e8abc6-4675-5cf3fc5b9b14/1:( 1184922337280 -->  1184930725888)]
[    20971520:    15728640] --> [VMFS -- LVID:56bacca5-61a9bfe9-c083-5cf3fc5b9b14/56bacca5-51e8abc6-4675-5cf3fc5b9b14/1:( 1184930725888 -->  1184946454528)]


so above logs indicate its all due to corruption @datasore level ?
If Yes -How can we resolve/fix it with minimal efforts and avoid such issue in future ?
If No -How to locate exact issue behind it....
>any tool we can use in running infra  ?
> due to VAAI feature enabled on newly formated lun
>due to in place upgrade
>due to SAN firmware upgrade
>due to patching  of vc/esxi and vms pending since long time including vmtool alos
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
if you cannot answer that question yourselves.

MOVE THE VMs OFF IMMEDIATELY.
0
patronAuthor Commented:
we did vmfs upgrade almost  6 month before and it was  90% we did in place upgrade but 10% we did from scratch adding new luns

earlier we had few orphaned disk..but now days [in june-july]getting more and more

how can we control on creation of such orphaned n ghost files
0
patronAuthor Commented:
i believe its not lun/datasore corruption , can we use any better tool to look n fix more on this within running infra
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
NONE.

orphaned disks are not as a result of a corrupt datastore.

what makes you think they are orphaned ?  are they really not in use.

if you have doubts about a datastore , you should move all the VM off it, and see what remains.

and then delete/remove/re-create.
0
patronAuthor Commented:
Thanks Andrew

yes will check for that, i am not directly involved team in this issue,else i could have done more,but will try for sure

Many Thanks for all your support on this.

let me try to look more into this
0
patronAuthor Commented:
can we remove this question ?
0
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Why, select an Answer and Award Points.
0
patronAuthor Commented:
Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.