VirtualMAN
Cadet
- Joined
- Mar 6, 2016
- Messages
- 1
Hi everybody,
I am new to the forum but I read it since years, you was so useful that I decided to post about a problem that I identified, lot of people wondering about that on the net so this is my way to say thanks :)
my enviroment is freenas 9 on esxi, hdd is zfs on a vmdk as big as the hdd but I feel this is "always" valid, this feeling is because I read a lot on this error and people has it on multiple setup, this explanation explains any of those problem (on paper).
if your freenas gives the error on subject the problem is probably corrupted files.
my advice is: copy every single file in the pool elsewere and it will hang at the corrupted file, reset nas, move the file in a folder inside the same pool (I called it problematic files) and go further with other files. I did it using cifs share so I read the file name on my windows machine when it hangs.
Hope it will be useful, sorry for my english and lack of technical details.
Now a question: is there any way to recover the files in my problematic files folder? I am not really interested because I have backups but you know murphy, better know it.
and a curiosity: wasnt zfs supposed to avoid that? I think this was because of powerdown but I experienced it on a 60gb file as soon as I copied inside the pool: no error on writing it, hangs when I read it, solved reuploading the file. Please note I removed scrubs (thanks to the virtualization guide here).
I am new to the forum but I read it since years, you was so useful that I decided to post about a problem that I identified, lot of people wondering about that on the net so this is my way to say thanks :)
my enviroment is freenas 9 on esxi, hdd is zfs on a vmdk as big as the hdd but I feel this is "always" valid, this feeling is because I read a lot on this error and people has it on multiple setup, this explanation explains any of those problem (on paper).
if your freenas gives the error on subject the problem is probably corrupted files.
my advice is: copy every single file in the pool elsewere and it will hang at the corrupted file, reset nas, move the file in a folder inside the same pool (I called it problematic files) and go further with other files. I did it using cifs share so I read the file name on my windows machine when it hangs.
Hope it will be useful, sorry for my english and lack of technical details.
Now a question: is there any way to recover the files in my problematic files folder? I am not really interested because I have backups but you know murphy, better know it.
and a curiosity: wasnt zfs supposed to avoid that? I think this was because of powerdown but I experienced it on a 60gb file as soon as I copied inside the pool: no error on writing it, hangs when I read it, solved reuploading the file. Please note I removed scrubs (thanks to the virtualization guide here).