serious vinum bug in 4-10 RELEASE?
Steve Shorter
steve at nomad.lets.net
Sun Jul 11 11:48:12 PDT 2004
Howdy!
I have 4 identical disks, labels etc are also identical.
It looks like vinum after reboot does not recognize drives
properly, as it did immedialtely after initial configuration.
One drive/subdisk in each plex isn't recognized, and the other one
is duplicated, which destroys the mirror.
I created 2 vinum volumes with
# vinum create -f /etc/vinum.raid1
and the following config file
drive data0 device /dev/da0d
drive data1 device /dev/da1d
drive data2 device /dev/da2d
drive data3 device /dev/da3d
volume mq0 setupstate
plex org concat
sd length 0 drive data0
plex org concat
sd length 0 drive data2
volume mq1 setupstate
plex org concat
sd length 0 drive data1
plex org concat
sd length 0 drive data3
after running
# vinum lv -r -v
I get (correctly)
Volume mq0: Size: 18341345792 bytes (17491 MB)
State: up
Flags:
2 plexes
Read policy: round robin
Plex mq0.p0: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq0
Plex mq0.p1: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq0
Subdisk mq0.p0.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq0.p0 at offset 0 (0 B)
Drive data0 (/dev/da0d) at offset 135680 (132 kB)
Subdisk mq0.p1.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq0.p1 at offset 0 (0 B)
Drive data2 (/dev/da2d) at offset 135680 (132 kB)
Volume mq1: Size: 18341345792 bytes (17491 MB)
State: up
Flags:
2 plexes
Read policy: round robin
Plex mq1.p0: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq1
Plex mq1.p1: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq1
Subdisk mq1.p0.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq1.p0 at offset 0 (0 B)
Drive data1 (/dev/da1d) at offset 135680 (132 kB)
Subdisk mq1.p1.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq1.p1 at offset 0 (0 B)
Drive data3 (/dev/da3d) at offset 135680 (132 kB)
After rebooting the system and running
# vinum lv -r -v
I get the following incorrect configuration. Notice that
drives data0 and data1 are missing and drives data2 and data3 are
duplicated where data0 and data1 should be.
Volume mq0: Size: 18341345792 bytes (17491 MB)
State: up
Flags:
2 plexes
Read policy: round robin
Plex mq0.p0: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq0
Plex mq0.p1: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: flaky
Organization: concat
Part of volume mq0
Subdisk mq0.p0.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq0.p0 at offset 0 (0 B)
Drive data2 (/dev/da2d) at offset 135680 (132 kB)
Subdisk mq0.p1.s0:
Size: 18341345792 bytes (17491 MB)
State: reborn
Plex mq0.p1 at offset 0 (0 B)
Drive data2 (/dev/da2d) at offset 135680 (132 kB)
Volume mq1: Size: 18341345792 bytes (17491 MB)
State: up
Flags:
2 plexes
Read policy: round robin
Plex mq1.p0: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mq1
Plex mq1.p1: Size: 18341345792 bytes (17491 MB)
Subdisks: 1
State: flaky
Organization: concat
Part of volume mq1
Subdisk mq1.p0.s0:
Size: 18341345792 bytes (17491 MB)
State: up
Plex mq1.p0 at offset 0 (0 B)
Drive data3 (/dev/da3d) at offset 135680 (132 kB)
Subdisk mq1.p1.s0:
Size: 18341345792 bytes (17491 MB)
State: reborn
Plex mq1.p1 at offset 0 (0 B)
Drive data3 (/dev/da3d) at offset 135680 (132 kB)
Ideas?
-steve
"The age of the Internet has a right to its own music"
http://www.linuxsuite.org
More information about the freebsd-questions
mailing list