This thing is a real curse...
After recently spending a couple of weeks of hard work, my OVM 2.1.5 setup WAS fully functional with Multipath. Also the root device correctly multipathed (physical servers are diskless and booting from SAN), everything working nicely.
For the whole story, if interested, pls. see
948143
Now OVM 2.2 is out and I thought it would have been much easyer to configure the same way. Looks like it's going to be much harder.
In a matter of fact, if I freshly install the system using the "linux mpath" option, everything SEEMS to go straight and easy. No errors, nothing. But at the end of installation, when I reboot, I get the following errors on the console screen:
/bin/true exitted with 255
error calling out /bin/true
not enough space for response from /bin/true
/bin/true exitted with 255
error calling out /bin/true
DM message failed [queue_if_no_path
]
No devices found
And a bit later:
Checking filesystems
fsck.ext3: Nosuch file or directory while trying to open /dev/mapper/mpath0p2
/dev/mapper/mpath0p2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an etx2 filesystem... (blah blah blah)
Then I'm dropped to a shell where I'd be supposed to do an fsck, but there's obviously NOTHING to be checked... It's just that it doesn't work!
Pls note that:
- As suggested by Avi in the thread I mentioned in the beginning, I'm installing presenting ONE SINGLE LUN to the host at installation time (planning to add the others later)
- I can't even boot in Single User Mode, it just doesn't change
- If I activate a single FC path to the install LUN, it works, but the root device won't be multipathed, so that's not an option
And finally, a curios fact: if I UPGRADE the 2.1.5 setup instead of doing a fresh install, IT WORKS... But I have errors mounting the shared storage, it says that:
Starting OVS Storage Repository Mounter...
/etc/rc3.d/S95ovsrepositories: line 111: /etc/ovs/repositories: No such file or directory
OVS Storage Repository Mounter Startup: [OK]
But then, ok, it boots correctly... But the OVS repository is not mounted anymore!
So I tried to go in /etc/ovs, and I saw there was a "repositories.bak" file... Renamed it "repositories" and tried to boot again...
Result:
Starting OVS Storage Repository Mounter...
Mounting repository @8AD102FF48844D6B8663F90F8279726A from ... usage: /usr/lib/ovs/ovs-onlinerepo <uuid> <source>
...
OVS Storage Repository Mounter Startup: [FAILED]
Any ideas?
Opening an SR is not an option because I bought ULN 2 months ago but still they don't deliver my CSI.
I'd like to be able to do a fresh install anyway. Upgrading would maybe easier to solve, but what if I'll add another server to the rig?
Thanks in anticipation for any useful insight/idea...