Is multipath essential on Server 20.04?

Liam Proven lproven at gmail.com
Fri Oct 2 19:58:15 UTC 2020


On Fri, 2 Oct 2020 at 20:50, R C <cjvijf at gmail.com> wrote:
>
> multipath is needed for (optimizing) io when there are virtual storage
> devices that use multiple hardware/actual devices (hence multipath), for
> example when you are using lustre, scality, san, jbod, ZFS or 'any array'
>
> since you are using ZFS, in/on an array, it would be a good idea to use it.
>
> You don't NEED to use it, it only makes io more efficient and probably
> faster.
>
> Also, you can shut down some of the cores on your RPI cpu, you DON'T
> really need those either.

Thanks for the comments.

My impression was that it was for SAN connections -- things like
iSCSI, and maybe Ceph. I don't know much about Lustre/Glustre, and
I've never even heard of Scality before. JBOD? Just a Bunch of Disks?
Really? How so?

ZFS I'm using, yes, which is why I was concerned. If I end up dropping
ZFS then I'll probably replace it with a plain old MDRAID. Both are
multi-device filesystems, so I figured they'd need the kernel
devicemapper, but I don't see why ZFS on a single box that's not
connecting to anything else should need it. How come?

(Obligatory "please bottom-post on the list" comment, too...)


-- 
Liam Proven – Profile: https://about.me/liamproven
Email: lproven at cix.co.uk – gMail/gTalk/gHangouts: lproven at gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053




More information about the ubuntu-users mailing list