It occurs to me that old (circa 2005) kernels (and even old user-space tools) cannot handle large system minor numbers. So please consider that.
No, using an AoE (major, minor) address space that is sparsely populated is OK. Large gaps in the address space don't mean that you run into a limit sooner when dynamic system minor numbers are in use.
There should be no advantage in using the static system minor numbering. That feature was added for backward compatibility.
On Mar 31, 2014, at 2:47 PM, James R. Leu <jleu@xxxxxxxx> wrote:
> Thank you for your response.
>
> Have I over extended the dynamic minor number allocation system by
> having AOE devices on one server many shelves apart?
>
> IE 0.1 and 19.10
>
> Since I track my AOE assignments carefully, would I be better served
> by turning off dynamic minor number allocation and maintain the
> /dev/etherd/ devices with the mk_shelf script?
>
> On Fri, Mar 28, 2014 at 08:55:09PM +0000, Ed Cashin wrote:
>> Just some quick thoughts in a hurry...
>>
>> Talking about minor numbers is naturally confusing with the aoe driver, because there are at least two kinds:
>>
>> * The AoE address is comprised of a {major, minor} pair, often called shelf.slot. "AoE minor number"
>>
>> * The Linux system has special block device files with major and minor numbers. "system minor number"
>>
>> For dynamic system minor numbers, which is the default (but see `cat /sys/module/aoe/parameters/aoe_dyndevs` to verify), there is a bitmap of available system minor numbers. There are over 64000 of them, but you could run out if you have AoE targets coming and going and you don't do aoe-flush.
>>
>> If you're doing static system minor numbers, though, you'd expect higher AoE minor numbers to be a problem.
>>
>> On Mar 28, 2014, at 3:14 PM, James R. Leu <jleu@xxxxxxxx> wrote:
>>
>>> Hello,
>>>
>>> I'm using AOEv83 on my client machines and vbladev20 on my AOE Server.
>>> Occasionally when I start a new vblade on the server, the client will
>>> see the new aoe device, but attempts to mount it result in
>>> mount returning 'unknown device'. If I relaunch vblade with different
>>> shelf/slot numbers it will mount fine.
>>>
>>> After unloading/reloading the aoe module on the client I am able to
>>> use the original shelf/slot numbers without a problem.
>>>
>>> In the situation where it fails the minor number is really high.
>>> ex 152.3584
>>>
>>> when I use different shelf slot numbers, the minor number
>>> looks like I would expect
>>> ex 152.290
>>>
>>> Has anyone else seen this?
>>> Is there a limit to he minor number that aoe uses?
>>>
>>> Thank you for your time.
>>>
>>> --
>>> James R. Leu | Systems and Development | INOC | Madison, WI, USA
>>> Service. Not Software.®
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Aoetools-discuss mailing list
>>> Aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
>>> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
>>
>
>
> --
> James R. Leu | Director of Technology | INOC | Madison, WI, USA
> O: +1-608-204-0203 | F: +1-608-663-4558 | jleu@xxxxxxxx | www.inoc.com
> Service. Not Software.®
------------------------------------------------------------------------------
_______________________________________________
Aoetools-discuss mailing list
Aoetools-discuss@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
