Hello Adrian,

> I'm going to be building a new, dedicated fileserver soon, which will
> feature a more formal arrangement shared across more servers and
> clients.

I would suggest you consider a volume naming model where a volume name is
just its mountpoint path. Volume names may include '/' so the root volume
can rather logically be called "/" and so on.

It makes it a way easier to map volumes to paths and the other way around.

Unfortunately there still is a 32-chars limitation on the volume name
length, but it may be lifted in the future (I hope).
With not-too-deep mountpoints paths it is no problem.

Regards,
--
Ivan


Reply via email to