Volume Corrupted?
One of my nexenta volumes is a deduped store on a NAS that is itself a RAID device. It's very slow. I had the volume configured with faster/local cache and logs and a 2TB vmdk (vmware) that just happened to live on the NAS. the NAS is supposed to be a grab-n-go DR device, so I was happy if would just slog along and receive syncs from more capable setups.
Lately, the dedup ratio jumped from 15:1 to 167,000:1. (not a typo). According to VMware, the NFS mount has over 1 billion terabytes (1.06EB, I wish). I have no idea what sort of issues might crop up because of that. Hopefully VMware won't fall over due to a limit being reached somewhere.
The volume is readable and writable but it sure looks like corruption and a learning opportunity. I have not encountered a data corruption issue, yet but I don't like the look of it.
I'm not super familiar with all the command line tricks. Anyone have suggestions for what might be done to rehabilitate the volume before I destroy it?
dedups_gone_wild.JPG (40 KB)