Deadpan110 Posted August 10, 2016 Share Posted August 10, 2016 Hi all, I am currently testing my setup, I have as follows: unRAID: 1 x 2TB Parity Device 3 x 1TB Array Disks Cache: 1 x 120 GB SSD Unassigned Devices: 1 x 2TB HDD So far I have been figuring out my way around, I am not used to slackware or the inner most workings of unRAID but have had plenty of experience in Gentoo, Debian and Ubuntu in the past so will not shy away from things that are too technical. Basically I only use my unRAID cache device for appdata, domains and system folders - only using the Cache Disk and not the unRAID array. So here goes my experimental beginnings... I have successfully added the bcache module into the kernel and have added the bcache-tools. I then set up my unassigned device to be a LVM volume group. My idea is that I am able to host larger domains by using bcache devices backed by LVM logical volumes (makes it easy to flush dirty data from bcache and then snapshot the logical volume if I ever want to create backups and copy them onto the array for safe keeping at regular intervals). All the above sounds like fun and I am about to start testing to see how it all works and how stable it is. My question to the community is about the unRAID cache device... It would be nice if I could set it from using sdx to bcache0 - obviously there will be performance loss with bcache (especially more so before the cache is warmed up). Is there anything I can change to force unraid to use a different device (bcache) as I would still like my appdata and system to be stored in /mnt/cache (and still have transparency with /mnt/users if I ever need it)? TL;DR Tell unRAID to use /dev/bcache0 instead of /dev/sdj as the cache device? Thanks in advance! Quote Link to comment
BRiT Posted August 10, 2016 Share Posted August 10, 2016 Nothing that you can change. All you can do is submit a feature requestto the fine folks at LimeTech. Quote Link to comment
Squid Posted August 10, 2016 Share Posted August 10, 2016 Thinking out loud here, so nothings tested What about not assigning the cache drive at all via the UI, and then do a link to /mnt/cache. (Or mount it at /mnt/cache) Quote Link to comment
Deadpan110 Posted August 10, 2016 Author Share Posted August 10, 2016 Nothing that you can change. All you can do is submit a feature requestto the fine folks at LimeTech. Nice, It would be easier if the bcache module was included in the kernel compile too (for crazy ppl like myself to play with) Thinking out loud here, so nothings tested What about not assigning the cache drive at all via the UI, and then do a link to /mnt/cache. (Or mount it at /mnt/cache) Yes, I will try that... I can live without /mnt/cache being included in /mnt/user (and not included in /mnt/user0), but was curious how it worked... I will try it and report back any findings Quote Link to comment
Squid Posted August 10, 2016 Share Posted August 10, 2016 Or maybe assign the disk to cache, at array start, umount it, and then mount bcache0 at /mnt/cache. Should let you keep user0 and have /mnt/cache integrated into user. Quote Link to comment
kubed_zero Posted February 19, 2017 Share Posted February 19, 2017 Was this ever tested or worked on? Any updates in the UnRAID kernel? I think my use case could benefit from an SSD read cache (serving relatively repeated data and not wanting parity and D1/2 spun up all the time) and this is the only UnRAID related info I could find on the matter. Quote Link to comment
gilahacker Posted October 27, 2017 Share Posted October 27, 2017 Bump. A Bcache SSD would be nice to have to prevent drive spinup for reads of frequently accessed files, and cheaper than throwing more RAM at a system and hoping the Linux filesystem cache takes care of it. I'm not sure if Bcache would be compatible with unRAID or if changes would have to be made to unRAID itself. I haven't dug into Linux filesystem caching much to see if it's even possible but it'd be nice to have read caching turned off for the normal unRAID write cache SSD as well, if it's not already. I don't want free RAM being used to cache that drive when it could be better spent caching the spindles in the array. A quick Google search indicates that mounting a disk with the "sync" option disables write caching, but read caching seems to be a separate thing. On my unRAID server the mount options are the same for the SSD and array drives (xfs, rw, noatime, nodiratime, 0 0). Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.