patron
asked on
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 ?
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 ?
You can use RV Tools, to check for orphaned files and delete them, if not in use.
http://www.robware.net/
http://www.robware.net/
ASKER
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 ?
is it related to ghsot file and what could be done to get this fixed ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, they r not in use,but yet not able to delete n files are like log files n vmdk etc not in use??
log files from what ?
screenshots please
screenshots please
ASKER
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 ??
you need to check if they are in use, does RV Tools suggest they are orphaned.
ASKER
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 ?
>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 ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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 ?
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 ?
Yes, you can use VOMA to check for VMFS corruption.
ASKER
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 ?
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 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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-c08 3-5cf3fc5b 9b14/56bac ca5-51e8ab c6-4675-5c f3fc5b9b14 /1:( 1184909754368 --> 1184922337280)]
[ 12582912: 8388608] --> [VMFS Z- LVID:56bacca5-61a9bfe9-c08 3-5cf3fc5b 9b14/56bac ca5-51e8ab c6-4675-5c f3fc5b9b14 /1:( 1184922337280 --> 1184930725888)]
[ 20971520: 15728640] --> [VMFS -- LVID:56bacca5-61a9bfe9-c08 3-5cf3fc5b 9b14/56bac ca5-51e8ab c6-4675-5c f3fc5b9b14 /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
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-c08
[ 12582912: 8388608] --> [VMFS Z- LVID:56bacca5-61a9bfe9-c08
[ 20971520: 15728640] --> [VMFS -- LVID:56bacca5-61a9bfe9-c08
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
if you cannot answer that question yourselves.
MOVE THE VMs OFF IMMEDIATELY.
MOVE THE VMs OFF IMMEDIATELY.
ASKER
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
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
ASKER
i believe its not lun/datasore corruption , can we use any better tool to look n fix more on this within running infra
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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
ASKER
can we remove this question ?
Why, select an Answer and Award Points.
ASKER
Thanks
ASKER
What could be reason behind it ?