2009/6/3 Juergen Keil <[email protected]>:

> I'm not yet sure why it doesn't work with "xvda" on the disk config line,
> and /xpvd/x...@51712:a as the bootpath, but I can reproduce the same
> "NOTICE: spa_import_rootpool: error 22" error when using such a config.

Apparently you gets this error when the "phys_path" for the disk
in the zpool disk label doesn't point to the disk's current physical
device path, e.g. because the frontend device was changed in the
python disk config.

Can be fixed by booting from the livecd media, with the disk at the new
frontend location, and doing a "zpool import -f rool".  This updates the
phys_path in the zpool's label.  The phys_path in the label can be
checked using the command "zdb rpool".
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to