--- Jeff Garzik <jeff@xxxxxxxxxx> wrote:
> Luben Tuikov wrote:
> > What is needed is persistence, regardless of reboots of what OS
> > is running on the host CPU/system. SAS WWNs are properties of
> > the SAS target/initiator port, they are not properties of when
> > the host system was booted, or what OS is running on it.
>
>
> As part of the previously described schemes, the admin is certainly
> allowed to choose an option (manual WWN specification) that enables an
> external system of persistance.
>
> But such a system should not be a /requirement/, when all an admin might
> want to do is simply get their card working.
It *is* a requirement, in fact at all levels of the product.
How would you query the storage domain (at boot time mind you) that
no such WWN exists, and/or will not exist when another storage component
is connected to or comes online, if you generated it in the kernel?
SAS ports not having a WWN as part of the MS/NVRAM is an *exception*,
and a bad one at that. The driver should just complain and not bring
up the HA.
Your "want to get their card working" way of view is very
simplistic to justify generating and assigning SAS WWN in the kernel.
This is the job of the manufacturer/packager, not the host OS.
Luben
>
> The admin knows whats best for their site, and may choose.
>
> Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
