- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The damage is 8 LBAs (4k) in megabyte 497043 (485GB away from the start of the volume), so it must be the data zone of the file system, correct? We know exactly what the LBAs are and we've verified that they most likely contain invalid data in them. Can we find what the file sits on top of those LBAs? What kind of tools either VMware or 3rd party that can provide insight here?
Again, I think it makes sense to try this approach first before we try more painful, labor intensive things, because knowing what file owns those LBAs can open up new possibilities: the file might be an old and not used, or it might be an empty space (as far as VMFS is concerned). And even if we see that VMDK of a production VM sits there doing V2V will have to be applied to a single VM, not to all VMs that have leg in the datastore.
Thanks a lot!