-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to emulate a larger SSD size #19
Comments
Hi, If your disk image size matches the size in the configuration file, it should be fine. Make sure sim_ssd_sz * (1 - OVP) >= 16GB here. The blackbox FTL you are using is no longer maintained, we created a new FTL specifically designed for FEMU model, checkout the newest commit in master branch. I suggest you use the new one. We will add some documents later. |
thank you for your quick response. since I've clearly did something wrong i thought it would be best if I'd eleborate on what I've done. also, I didn't quite understand what you meant here: thank you so much for your help. |
Oh, sorry, you can ignore this part .. I'm gonna close this issue, just in case u have more questions, feel free to re-open it, thx! |
What is the relationship between the device size as given in the QEMU command and and the device size as hard-coded into ftl.c? If the passed-in device size is smaller than the hard-coded device size, then is the difference equivalent to overprovisioned device capacity? A related issue: I set them to the same thing (devsz_mb=2048, which the FEMU OS reports as 2147483648 bytes, and the appropriate settings in ftl.c) and I see the following: |
Hey there,
I'm currently trying to use your system with an SSD size of 16GB while running on the black-box mode.
I've tried changing it inside the black-box script and inside the ssd1.conf file but I keep getting the error message "exceed sector number".
what changes should i make in the ssd1.conf file so it'll be compatible to the size I've set in the NVMEIMGSZ variable inside the black-box script ?
The text was updated successfully, but these errors were encountered: