Re: [Aoetools-discuss] AOE v83 - unknown device

[Ed C. <ec...@co...>]

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 <jl...@in...> 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
> Aoe...@li...
> https://lists.sourceforge.net/lists/listinfo/aoetools-discuss