You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
All
In RancherOS fdisk -l reports 16 ram disks (/dev/ram0 ... /dev/ram15), other Linux distributions do not output ramdisk information.
The RAM disk driver is a way to use main system memory as a block device. It is required for initrd, an initial filesystem used if you need to load modules in order to access the root filesystem (see Documentation/initrd.txt). It can also be used for a temporary filesystem for crypto work, since the contents are erased on reboot.
To do list:
Block RAM disk module (brd, CONFIG_BLK_DEV_RAM) compiled as 'y', that means it is 'built-in' and can not be unloaded or loaded with different parameters. This render module completely useless because user can not anymore change it size. We should change it back to 'm' (module) to allow users use this module.
Turn on and off at the right time.
The text was updated successfully, but these errors were encountered:
RancherOS Version: (ros os version)
v1.1.3
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
All
In RancherOS
fdisk -l
reports 16 ram disks (/dev/ram0
.../dev/ram15
), other Linux distributions do not output ramdisk information.The RAM disk driver is a way to use main system memory as a block device. It is required for initrd, an initial filesystem used if you need to load modules in order to access the root filesystem (see Documentation/initrd.txt). It can also be used for a temporary filesystem for crypto work, since the contents are erased on reboot.
To do list:
The text was updated successfully, but these errors were encountered: