Date: Thu, 11 Nov 2004 00:32:18 +0200 From: Kim Helenius <tristan@cc.jyu.fi> To: freebsd-questions@freebsd.org Subject: A fundamental vinum raid5 problem Message-ID: <419296F2.3060709@cc.jyu.fi>
next in thread | raw e-mail | index | archive | help
I have an absurd problem with vinum. I use the following command:
vinum create blob.conf
blob.conf:
drive d1 device /dev/ad4s1d
drive d2 device /dev/ad5s1d
drive d3 device /dev/ad6s1d
drive d4 device /dev/ad7s1d
volume blob
plex org raid5 433k
sd length 0 drive d1
sd length 0 drive d2
sd length 0 drive d3
sd length 0 drive d4
After this I get the following output:
4 drives:
D d1 State: up /dev/ad4s1d A: 0/286181 MB (0%)
D d2 State: up /dev/ad5s1d A: 0/286181 MB (0%)
D d3 State: up /dev/ad6s1d A: 0/286181 MB (0%)
D d4 State: up /dev/ad7s1d A: 0/286181 MB (0%)
1 volumes:
V blob State: down Plexes: 1 Size: 838 GB
1 plexes:
P blob.p0 R5 State: init Subdisks: 4 Size: 838 GB
4 subdisks:
S blob.p0.s0 State: empty D: d1 Size: 279 GB
S blob.p0.s1 State: empty D: d2 Size: 279 GB
S blob.p0.s2 State: empty D: d3 Size: 279 GB
S blob.p0.s3 State: empty D: d4 Size: 279 GB
So far everything looks fine. Even vinum printconfig looks all right to me:
# Vinum configuration of e26b.mylly.jyu.fi, saved at Wed Nov 10 23:49:11
2004
drive d1 device /dev/ad4s1d
drive d2 device /dev/ad5s1d
drive d3 device /dev/ad6s1d
drive d4 device /dev/ad7s1d
volume blob
plex name blob.p0 org raid5 866s vol blob
sd name blob.p0.s0 drive d1 plex blob.p0 len 586098408s driveoffset 265s
plexoffset 0s
sd name blob.p0.s1 drive d2 plex blob.p0 len 586098408s driveoffset 265s
plexoffset 866s
sd name blob.p0.s2 drive d3 plex blob.p0 len 586098408s driveoffset 265s
plexoffset 1732s
sd name blob.p0.s3 drive d4 plex blob.p0 len 586098408s driveoffset 265s
plexoffset 2598s
Well, then, I type vinum stop and vinum start. Now vinum printconfig shows:
# Vinum configuration of e26b.mylly.jyu.fi, saved at Wed Nov 10 23:52:06
2004
drive d4 device /dev/ad7s1d
drive d3 device /dev/ad6s1d
drive d2 device /dev/ad5s1d
drive d1 device /dev/ad4s1d
Which means my config just disappeared. (Earlier I did vinum init to
initialize the raid5 as recommended. I mounted, copied some data on it
and rebooted. After reboot it was gone. Init took three hours so I
decided to test the short way.)
So next I tested a setup that would take a little less time:
vinum -> concat -v /dev/ad4s1d /dev/ad5s1d
volume vinum0
plex name vinum0.p0 org concat
drive vinumdrive0 device /dev/ad4s1d
sd name vinum0.p0.s0 drive vinumdrive0 size 0
drive vinumdrive1 device /dev/ad5s1d
sd name vinum0.p0.s1 drive vinumdrive1 size 0
V vinum0 State: up Plexes: 1 Size: 558 GB
P vinum0.p0 C State: up Subdisks: 2 Size: 558 GB
S vinum0.p0.s0 State: up D: vinumdrive0 Size: 279 GB
S vinum0.p0.s1 State: up D: vinumdrive1 Size: 279 GB
newfs /dev/vinum/vinum0
...
Mounted and seems to work. Vinum stop, vinum start... gone. I can
recreate it with the concat command but surely this is not how it's
meant to be? I've actually created a concat vinum volume on another
install earlier and it works.
Current setup:
FreeBSD e26b.mylly.jyu.fi 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Mon Nov 8
21:43:07 EET 2004 tristan@e26b.mylly.jyu.fi:/usr/obj/usr/src/sys/KIUKKU
i386
I've read about problems with vinum in 5.3 (already got the dangling
vnode panic and lost some data in the following confusion) but I would
be very satisfied if I could start vinum and mount the volume with a
script after boot process. But why is the configuration disappearing?
vinum saveconfig doesn't help either.
Thanks in advance,
--
Kim Helenius
tristan@cc.jyu.fi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419296F2.3060709>