Regression #14351
closed
Ram Disks are not created at boot.
Added by Steve Wheeler over 1 year ago.
Updated over 1 year ago.
Category:
Operating System
Plus Target Version:
23.05
Release Notes:
Force Exclusion
Affected Architecture:
All
Description
RAM disks fail to be created at boot showing the alert:
New alert found: RAM disk creation failed. Reverted to traditional storage. Check RAM disk sizes.
This appears unrelate to the actual available RAM sizes. Affects all architectures.
Tested: 23.05.r.20230504.1544 and 2.7.0.a.20230504.0600
- Assignee set to Jim Pingle
I was seeing that when I had the RAM disk size set larger than the free memory (but smaller than RAM+SWAP) but not when there was enough free RAM to hold the disks.
See #13508 for some more info there on why it's tricky to solve that case.
It's possible my last change there introduced a new bug, but it was working on my test system before I committed it.
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Release Notes changed from Default to Force Exclusion
This was indeed broken by my last change on #13508 somehow. Since that fix was only partial anyhow, reverting that is the best way to fix this since the old code was working and a better fix is going to be more risky at this stage.
- Related to Todo #13508: Uncouple RAM Disk size from available kernel memory added
seeing tmpfs for /tmp and /var according to the dashboard widget with 23.05.r.20230505.1836
- Status changed from Feedback to Resolved
Same here. On a system where I hit that error on the previous builds, a current build works without error. RAM disks are mounted and working.
Also available in: Atom
PDF
Updated by 
Updated by