![]() Ramdisks are already quite a niche topic.ītw I'm using Debian Testing, which at the time of writing is the testing branch ahead of Debian 10.Įdit: I do not write back to this disk, if it makes any difference. pipTheGeek at 17:39 pip Now, that would actually make some sense. I'm sure such a thing must be possible with linux - but I don't know what to search for. There is a RAM disk (sorry, cant remember its name) that allows you to use the memory above the 3GB limit on a 32bit OS to create a RAM disk. Is there a way to create a ramdisk in memory which caches data read from this external disk? This is quite inefficient, because the amount of data that I actually read is only about 1 GB. Create a 'small enough' system disk image using LVM (a minimized Oracle Linux installation does that) After the system is started, create a ramdisk and use it as a mirror for the system volume when/if the (primary) system disk access is lost, the ramdisk continues to provide all necessary system functions. However it may not work later on when I change to a different, larger dataset. This works ok, because the entire contents can fit into the amount of available memory that I have. Every time I reboot my system, I have to copy the contents of the disk back into this ramdisk. I created a ramdisk using a tmpfs filesystem to store a copy of the disk contents in memory to speed up the processing time required. There is about 6.5 GiB of data on the disk, but only a few files are processed rather than the entire contents. On Linux, you can toggle the behaviour with hdparm: /sbin/hdparm -W 0 /dev/hda 0 Disable write caching /sbin/hdparm -W 1 /dev/hda 1 Enable write caching. I've got some code that processes a load of data stored on an external HDD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |