Hannes Reinecke wrote:
> Vasu Dev wrote:
>> This is protect destroying fcoe interface while used
>> as root filesystem.
>>
>> Adds -r option to accept root interface name then sets up
>> rootfs flag for its associated fcoe_ports, that flag
>> is later used to ignore any subsequent FCOE_DESTROY
>> operation on root interface.
>>
> Hmm. So you never ever expect the rootfs to be multipathed?
>
> Not sure this is a clever design.
>
> I'd rather have it implemented via signal handlers;
> eg SIGTERM would should down fcoemon without shutting
> down running connections, and eg SIGUSR1 or SIGHUP
> would be shutting down all connections.
>
> This way we wouldn't have to explicitely specify the
> root fs via NIC. And we could be running the system
> on multipath.
>
> Cheers,
>
> Hannes
I agree. Also, there could be more than one critical disk.
So, maybe both approaches make sense. One that adds a flag
saying the disk is critical and one that lets fcoemon exit
without tearing down fcoe instances.
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
