Failure to boot if vitrual memory set to more than available space

[dlmcpaul]

If the virtual memory setting is greater than the amount of space available on disk then haiku stops booting.

If there is not enough space for the swap file then it should be reduced or virtual memory turned off.

Failing to boot should not be an option.

How to reproduce: Increase Virtual Memory to > available disk space and reboot.

experience behaviour: Haiku fails to boot

expected behaviour: Haiku boots with reduced swap space.

[axeld]

I can't reproduce this over here. Booting always works fine.

Can you please provide syslog from a working run, and from one that doesn't boot? (a photo of the last two pages off on screen debug output would be great from the latter)

[dlmcpaul]

Syslog from booting system

[axeld]

The syslog (unzipped would have been preferred for easier handling) from the booting system alone doesn't really help. In any case, since I cannot reproduce this, I don't think this deserves to be in the alpha milestone.

[scottmc]

Does this still happen?

[leavengood]

Taking ownership.

[leavengood]

I couldn't reproduce this either, and I tried pretty hard.

For one thing, the VirtualMemory preflet will only let you set the swap size to a maximum of the available space on the drive (though even that should be reduced.)

Secondly, even if the virtual_memory settings file is modified to use a size greater than the available space, the VM system will fail in resizing the swap file, and even prints a syslog error saying so: "Failed to resize /var/swap to 3546991104 bytes: No space left on device".

So I'm pretty satisfied this can be closed.