Hi, again
Just a quick update on my gvinum issues - this time installed a 8.0-RC1 system under Virtualbox - just to mention there's a lot work being done on gvinum
Now it includes some of the original vinum commands as well as some new like:
- attach
- concat
- detach
- grow
- mirror
- raid5
- stripe
This time I had some progress settings up the root filesystem on gvinum.
I've also used this documentation, section "Install FreeBSD on Vinum":
http://www.vinumvm.org/cfbsd/vinum.pdf
However not all of the steps were correct, for example:
1. Editing with bsdlabel is being done in a different manner
I had to first mount / and /usr then make a copy of the current labels (bsdlabel ad0s1 > /tmp/bsdlabel.orig). Then edit it as described in the document and save it in /tmp/bsdlabel.new. Then a reboot in single-user mode is required again in order to write the new labels, otherwise you get an error like this:
Code:
bsdlabel: Class not found
re-edit the label? [y]:
/tmp/bsdlabel.orig
Code:
# /dev/ad0s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 2097152 2097152 4.2BSD 0 0 0
b: 2097152 0 swap
c: 20964762 0 unused 0 0 # "raw" part, don't edit
d: 2097152 4194304 4.2BSD 0 0 0
e: 14673306 6291456 4.2BSD 0 0 0
/tmp/bsdlabel.new (changes in red)
Code:
# /dev/ad0s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 2097152 2097152 4.2BSD 0 0 0
b: 2096871 281 swap
c: 20964762 0 unused 0 0 # "raw" part, don't edit
d: 2097152 4194304 4.2BSD 0 0 0
e: 14673306 6291456 4.2BSD 0 0 0
h: 20964746 16 vinum
Write the new labels after booting in single-user mode again:
Code:
bsdlabel -R ad0s1 /tmp/bsdlabel.new
This is where bsdlabel is showing up some errors, although the new labels are written.
Code:
vnode_pager_getpages: I/O read error
vm_fault: pager read error, pid 21 (bsdlabel)
pid 21 (bsdlabel), uid 0: exited on signal 1
Segmentation fault
Then I had to power-off the system since, it was not operating anymore and go to single-user mode again.
After that you can create your gvinum volumes/drives/subdisks/plexes and make an fsck against the created volumes - everything fine so far.
Added 'geom_vinum_load="YES"' to /boot/loader.conf and rebooted once again.
However upon boot the system is not able to find the root filesystem.
Screenshot here:
http://unix-heaven.org/gfx/gvinum-fbsd-root-fs.png
Even settings the vfs.root.mountfrom* variables from the loader prompt doesn't help much. I had to enter
ufs:/dev/ad0s1a and the root filesystem is mounted again. However when I check the mounted filesystems - /usr, /var/, etc.. are all mounted using the gvinum volumes, except for root.
Seems that during boot the root filesystem cannot be found when it is used under gvinum.
Is anyone running a root filesystem under gvinum? Any ideas where to look for from now on?
Thanks!