Date: Wed, 11 Jan 2006 06:58:34 -0500 (EST) From: "Brian Szymanski" <ski@mediamatters.org> To: "Stijn Hoop" <stijn@win.tue.nl> Cc: freebsd-stable@freebsd.org, Lukas Ertl <le@FreeBSD.org> Subject: Re: gvinum/vinum on 6.0 Message-ID: <3657.68.49.189.193.1136980714.squirrel@68.49.189.193> In-Reply-To: <20060111064349.GJ63938@pcwin002.win.tue.nl> References: <2178.68.49.189.193.1136950709.squirrel@68.49.189.193> <20060111064349.GJ63938@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_20060111065834_81162 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Stijn, thanks for your help, I'm getting closer... >> I took 6.0 for a test drive today and was disappointed to find that >> vinum/gvinum are still in disarray. For example there is a man page for >> vinum, but only a gvinum binary. gvinum help still lists lots of old >> vinum >> commands that are not implemented in gvinum. Lots of basic things I try >> from the gvinum prompt just tell me "not yet supported". > > Hmm. There is a manpage in 6-STABLE. And there are a few things that > don't work but I wouldn't call it "lots". Ah, a manpage! Progress... >> But most importantly, gvinum configuration (at least for a raid-5 plex) >> still doesn't persist across a reboot :( > > That's a bug; I think it might be related to compiling gvinum in the > kernel > as opposed to loading it from /boot/loader.conf. I also think there is a > fix already commited to 6-STABLE. Hmm, I upgraded to 6-STABLE and I'm still having the problem. Here's basically how it happens: gvinum create /etc/vinum.cnf newfs /dev/gvinum/VOLUME mount /dev/gvinum/VOLUME /mnt #screw with /mnt, everything works and is happy, yay! reboot At this point I call "gvinum l" (which loads geom_vinum.ko) by hand (after the reboot). My configuration mostly seems to persist - except or the "drives" section... One of two things happens here: Either a) The volumes/plexes appear down, the subdisks are stale. Additionally, /dev/gvinum is not there - suffice it to say I can't mount anything. b) Everything has status up (except the nonexistent drives). In this case as well, /dev/gvinum is not there - and I still can't mount anything. If I try to fix the configuration by gvinum rm'ing the volumes and plexes that are there, then reloading my vinum.cnf (gvinum create), either: a) everything seems to work b) the system panics Unfortunately there is no correlation between "gvinum l" output and whether the system panics or is happy when I run gvinum create again. Would I have better luck compiling gvinum into the kernel instead of loading the module? What do other folks who have successful config's do? Thanks in advance, Brian Brian Szymanski Software and Systems Developer Media Matters for America ski@mediamatters.org ------=_20060111065834_81162 Content-Type: application/octet-stream; name="vinum.r5.cf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="vinum.r5.cf" ZHJpdmUgYXBwbGUgZGV2aWNlIC9kZXYvYWQxZApkcml2ZSBiYW5hbmEgZGV2aWNlIC9kZXYvYWQy ZApkcml2ZSBvcmFuZ2UgZGV2aWNlIC9kZXYvYWQzZAoKdm9sdW1lIHJ2CiBwbGV4IG9yZyByYWlk NSAyODhrCiAgc2QgbGVuZ3RoIDEwMThtIGRyaXZlIGFwcGxlCiAgc2QgbGVuZ3RoIDEwMThtIGRy aXZlIGJhbmFuYQogIHNkIGxlbmd0aCAxMDE4bSBkcml2ZSBvcmFuZ2UKCg== ------=_20060111065834_81162 Content-Type: application/octet-stream; name="gvinum.before" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gvinum.before" MyBkcml2ZXM6CkQgb3JhbmdlICAgICAgICAgICAgICAgIFN0YXRlOiB1cAkvZGV2L2FkM2QJQTog Ni8xMDIzIE1CICgwJSkKRCBiYW5hbmEgICAgICAgICAgICAgICAgU3RhdGU6IHVwCS9kZXYvYWQy ZAlBOiA2LzEwMjMgTUIgKDAlKQpEIGFwcGxlICAgICAgICAgICAgICAgICBTdGF0ZTogdXAJL2Rl di9hZDFkCUE6IDYvMTAyMyBNQiAoMCUpCgoxIHZvbHVtZToKViBydiAgICAgICAgICAgICAgICAg ICAgU3RhdGU6IHVwCVBsZXhlczogICAgICAgMQlTaXplOiAgICAgICAyMDM1IE1CCgoxIHBsZXg6 ClAgcnYucDAgICAgICAgICAgICAgIFI1IFN0YXRlOiB1cAlTdWJkaXNrczogICAgIDMJU2l6ZTog ICAgICAgMjAzNSBNQgoKMyBzdWJkaXNrczoKUyBydi5wMC5zMiAgICAgICAgICAgICAgU3RhdGU6 IHVwCUQ6IG9yYW5nZSAgICAgICBTaXplOiAgICAgICAxMDE3IE1CClMgcnYucDAuczEgICAgICAg ICAgICAgIFN0YXRlOiB1cAlEOiBiYW5hbmEgICAgICAgU2l6ZTogICAgICAgMTAxNyBNQgpTIHJ2 LnAwLnMwICAgICAgICAgICAgICBTdGF0ZTogdXAJRDogYXBwbGUgICAgICAgIFNpemU6ICAgICAg IDEwMTcgTUIK ------=_20060111065834_81162 Content-Type: application/octet-stream; name="gvinum.after" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gvinum.after" MCBkcml2ZXM6CgoxIHZvbHVtZToKViBydiAgICAgICAgICAgICAgICAgICAgU3RhdGU6IGRvd24J UGxleGVzOiAgICAgICAwCVNpemU6ICAgICAgICAgIDAgIEIKCjEgcGxleDoKUCBydi5wMCAgICAg ICAgICAgICAgUjUgU3RhdGU6IGRvd24JU3ViZGlza3M6ICAgICAwCVNpemU6ICAgICAgICAgIDAg IEIKCjMgc3ViZGlza3M6ClMgcnYucDAuczAgICAgICAgICAgICAgIFN0YXRlOiBzdGFsZQlEOiBh cHBsZSAgICAgICAgU2l6ZTogICAgICAgMTAxNyBNQgpTIHJ2LnAwLnMxICAgICAgICAgICAgICBT dGF0ZTogc3RhbGUJRDogYmFuYW5hICAgICAgIFNpemU6ICAgICAgIDEwMTcgTUIKUyBydi5wMC5z MiAgICAgICAgICAgICAgU3RhdGU6IHN0YWxlCUQ6IG9yYW5nZSAgICAgICBTaXplOiAgICAgICAx MDE3IE1CCg== ------=_20060111065834_81162--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3657.68.49.189.193.1136980714.squirrel>