Device mount times

[velis]

Hello,

I've been testing VirtualSAN for a bit now, so firstly, I'd like to congratulate you guys on this excellent product. I super love your thin-provisioned FS solution.

I have encountered one oddity while testing out the server. Please note that I'm a home user and am not really running this "by the spec" so to speak. My server is Win 7 HP with a simple RAID 5 array (4TB) and 4 GB of RAM (ordered an additional 8GB).

Anyway, the issues detected are these:
1. When out of memory, the service just stops, without any warning. I have seen the HW requirements which prompted me to order the additional RAM, but I still find this a bit odd that service would just terminate in such a case.
2. When service is started up, the volumes are mounting for minutes at a time. I mean, a really long time. Is this intended?

Thanks for your interest,
Jure

[Anatoly (staff)]

Hello,

I've been testing VirtualSAN for a bit now, so firstly, I'd like to congratulate you guys on this excellent product. I super love your thin-provisioned FS solution.

I have encountered one oddity while testing out the server. Please note that I'm a home user and am not really running this "by the spec" so to speak. My server is Win 7 HP with a simple RAID 5 array (4TB) and 4 GB of RAM (ordered an additional 8GB).

Anyway, the issues detected are these:
1. When out of memory, the service just stops, without any warning. I have seen the HW requirements which prompted me to order the additional RAM, but I still find this a bit odd that service would just terminate in such a case.
2. When service is started up, the volumes are mounting for minutes at a time. I mean, a really long time. Is this intended?

Thanks for your interest,
Jure

Thanks for the great feedback! We really appreciate this!
Ok, so one-by-one
1. Usually StarWind runs on the server where there is a lot of RAM, so we are not really considering this as the real life scenario. Moreover, StarWind HA protects from such kind of failures, soit is a good idea to get it if such issues may be the case.
2. Yup, that is OK. You are using LSFS, correct? When LSFS is starting StarWind basically chek all the data that is on the device.

I hope that helped.

[velis]

Yes, that helped. Anyway, the additiona 8GB RAM arrived today and testing is now much easier

I did experience a complete LSFS image corruption before, but I'm going to attribute that to low RAM I had before for now. The corruption was so huge that not even the partition was recognised on the mounted disk.

I have not detected any failures of any kind between last good mount and the corrupted mount. The service shut down normally (manually from local services admin tool).

[Anatoly (staff)]

Wow! Any chance you could share the logs with us?

[velis]

Of course, I'll try to locate them. If I load the log in console, it only loads log from last service start. (where) do you keep past logs? How do I deliver them (it was said not in the forums )?

[Anatoly (staff)]

Below is the default SW logs location:
C:\Program Files\StarWind Software\StarWind\logs