SOLVED Auto Rollback

edrube

Cadet
Joined
Dec 19, 2019
Messages
3
Hi everyone. The company where I work is currently running a FreeNAS-9.3-STABLE-201602031011 (yeah, 9.3). They also have a VM running Ubuntu 16.04, and using Webmin to control Samba server and his permissions.

It was working well until yesterday, when one of my coworkers told me that he can't enter to one directory. I went to check his permissions, but when I entered to his directory, it was empty. I started checking and many other directories/files are missing. One important thing is that this directories/files were "new" to the NAS, I mean, max 6 months old. The data was not fully deleted. Archives created 7 or more months ago are still there, but without the newest modifications.

So I think that NAS made a rollback. I'm not sure, because they don't have any snapshot or anything like that configured. I want to know, first if it is a rollback and why it happened. If that happened, is there any way that I can undo this rollback?

Am I missing something? Could it be an auto rollback? I'm pretty new to FreeNAS, Samba and stuff like that, so be free to correct or ask me anything.

Thanks for your time.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Could it be an auto rollback?
No, this is not something that exists in FreeNAS

is there any way that I can undo this rollback?
Not sure what happened, so can't be sure if it will be possible from FreeNAS itself... you said no snapshots, so it looks pretty unlikely.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
They are running an iSCSI too, maybe it is related with that?
It would seem to point to the OS that's mounting the iSCSI, so not FreeNAS (which is just hosting the blocks for the iSCSI target.
 

edrube

Cadet
Joined
Dec 19, 2019
Messages
3
It would seem to point to the OS that's mounting the iSCSI, so not FreeNAS (which is just hosting the blocks for the iSCSI target.

I figured out what happened.

I started to check vía Webmin, the iSCSI connections. There were many examples connections made by old IT coworkers, and for some reason, the Ubuntu mounted the wrong extent. Especifically, mounted an example connection made 6 months ago and unmounted the actual connection. I just mounted the correct one and voilá, problem solved.

Thanks for your help, your commentary made me check the Ubuntu.
 
Top