On 03/22/2011 11:38 AM, Daniel Kahn Gillmor wrote: > On 03/22/2011 10:47 AM, Hilko Bengen wrote: >> A server exports identical but separate AoE targets to a number of >> rather "dumb" clients, each on a separate VLAN. Separation using VLANs >> puts each client into its own broadcast domain, so I am able to present >> the same configuration to each client as far as AoE is concerned: From >> every client's point of view, the "disk" it accesses is AoE target e0.0. >> >> >> If I had used vblade-persist, only the first target could be >> successfully brought up since the symlink creation would fail for every >> target after that. > > Gotcha! OK, this finally makes sense to me, thanks for your > persistence. Sorry if i seemed thick-headed about it initially; having > your concrete example of the problem in a real-world case is really useful.
Hrm. After more thought, it looks to me like vblade-persist isn't going
to work in your scenario anyway, since vblade-persist only supports
exporting one instance of any given shelf/slot combination.
vblade-persist(8) says:
> BUGS
> You can't currently use the vblade-persist framework to export a device
> (or two) with the same shelf/slot identifier on two different network
> interfaces.
Maybe a fix to that underlying lack of a feature would need to address
the symlink issue.
Should we re-title this bug to "vblade-persist does not allow
simultaneous export of identical shelf/slot devices" ?
Is there another real-world instance where the symlinks cause problems?
--dkg
signature.asc
Description: OpenPGP digital signature
