Date: Thu, 20 Jun 2002 00:06:05 +0200 From: Marko Cuk <cuk@cuk.nu> To: stable@freebsd.org Subject: Vinum problems Message-ID: <3D11004C.F68E3B82@cuk.nu>
next in thread | raw e-mail | index | archive | help
Vinum is very bad when something goes wrong, obviously. I already see
Greg
groggy Lehey, how teach us all, read the manuals, send me debuugind
output,
do something, blah, blah.
Greg has done a big job, but Vinum remains same sof almost two years.
Nothing has changed. The website is all the same. No new functionality,
although they are in "progress".
Seriously, I am thinking not to use vinum on any disk, since it's
problems
and bad documentation when something goes bad. You must know, that vinum
is
maded for keeping large amount of data and therefore it sould be
reliable
and flexible. Vinim is not. Maybe I am stupid, but I am never sure, how
to
rescue some drive from loosing data.
It is nightmare and storage and disks are FreeBSD's big pain in the ass.
Here is my problem:
I had two - 2 - mirrored drives 36gig SCSI. Suddenly I have noticed,
that
one drive was down. I have started the mirror.p1.s0 and disk is
reviewing.
Ok....and after 51%, the box has crashed ?!
I changed the disk, try once more time, same resoult.
Setstate up .... helped me copy the data and put one normal disk instead
of
vinumed mirror and server is after 3 hours back online.
I have put disks into another server and now I am playing with
them...FreeBSD is 4.6
Here is the output:
p4# vinum l -v
2 drives:
Drive da2: Device /dev/da1s1e
Created on viharnik.xenya.net at Thu Feb 28 22:43:06
2002
Config last updated Wed Jun 19 15:35:21 2002
Size: 36701167104 bytes (35000 MB)
Used: 36701167104 bytes (35000 MB)
Available: 0 bytes (0 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 0
Drive da3: Device /dev/da2s1e
Created on p4.xenya.si at Wed Jun 19 13:53:16 2002
Config last updated Wed Jun 19 15:35:21 2002
Size: 36701167104 bytes (35000 MB)
Used: 135680 bytes (0 MB)
Available: 36701031424 bytes (35000 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 0
Drive *invalid*: Device
Created on at Thu Jan 1 00:00:00 1970
Config last updated Thu Jan 1 00:00:00 1970
Size: 0 bytes (0 MB)
Used: 0 bytes (0 MB)
Available: 0 bytes (0 MB)
State: referenced
Last error: none
Active requests: 0
Maximum active: 0
1 volumes:
Volume mirror: Size: 36701031424 bytes (35000 MB)
State: up
Flags:
2 plexes
Read policy: round robin
2 plexes:
Plex mirror.p0: Size: 36701031424 bytes (35000 MB)
Subdisks: 1
State: up
Organization: concat
Part of volume mirror
Plex mirror.p1: Size: 36701031424 bytes (35000 MB)
Subdisks: 1
State: faulty
Organization: concat
Part of volume mirror
2 subdisks:
Subdisk mirror.p0.s0:
Size: 36701031424 bytes (35000 MB)
State: up
Plex mirror.p0 at offset 0 (0 B)
Drive da2 (/dev/da1s1e) at offset 135680 (132 kB)
Subdisk mirror.p1.s0:
Size: 36701031424 bytes (35000 MB)
State: down
Plex mirror.p1 at offset 0 (0 B)
Drive *invalid* (*missing*) at offset 135680 (132 kB)
Can anyone explain me, how to delete invalid drive and how to "insert"
da3
to mirror ? As you can see, it is fully availiable for creating new
volumes,
but it won't become part of the mirror.
Here is the config file I have used for recreating 2nd mirror disk - da3
-
mirror.p1.s0
p4# less mi1
drive da3 device /dev/da2s1e
Many thanks, Marko Cuk
Chris Bolt wrote:
> I've been having nothing but problems with vinum ever since a disk
died
> two days after getting a RAID 5 array online. When I try vinum start,
I
> get the following:
>
> root@warhol:/home/chris# vinum start
> *** Warning: configuration updates are disabled. ***
> Warning: defective objects
>
> D d2 State: referenced Device Avail: 0/0 MB
> P raid5.p0 R5 State: degraded Subdisks: 2 Size: 55 GB
> S raid5.p0.s0 State: empty PO: 0 B Size: 55 GB
> S raid5.p0.s1 State: crashed PO: 0 B Size: 55 GB
> S raid5.p0.s2 State: empty PO: 1024 kB Size: 55 GB
> *** Warning: configuration updates are disabled. ***
>
> I don't get a warm fuzzy feeling when I see "empty" on my definitely
not
> empty RAID array. So let's try a list:
>
> root@warhol:/home/chris# vinum l
> 2 drives:
> D d1 State: up Device /dev/ad1s1e Avail: 0/57239 MB
(0%)
> D d3 State: up Device /dev/ad3s1e Avail: 0/57239 MB
(0%)
> D d2 State: referenced Device Avail: 0/0 MB
>
> 1 volumes:
> V raid5 State: up Plexes: 1 Size: 55 GB
>
> 1 plexes:
> P raid5.p0 R5 State: degraded Subdisks: 2 Size: 55 GB
>
> 3 subdisks:
> S raid5.p0.s0 State: empty PO: 0 B Size: 55 GB
> S raid5.p0.s1 State: crashed PO: 0 B Size: 55 GB
> S raid5.p0.s2 State: empty PO: 1024 kB Size: 55 GB
>
> What the? How do I fix d2? Keep in mind configuration updates are
> disabled, so I can't really change anything...
>
> And at one point, dumpconfig gave me the following, but I'm too scared
> to reproduce it:
>
> vinum -> dumpconfig
> Drive d1: Device /dev/ad1s1e
> Created on warhol.deviantart.com at Tue Jun 4
23:13:18
> 2002
> Config last updated Wed Jun 14 18:20:35 2000
> Size: 60019835904 bytes (57239 MB)
> volume raid5 state down
> plex name raid5.p0 state down org raid5 1024s vol raid5
> sd name raid5.p0.s0 drive d1 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 0s
> sd name raid5.p0.s1 drive d2 plex ò²u!¹ðððÔÁüòÀðвðò°0ñðððàô
> h`ñÆòòð0°ðàòòÄÞpøÜðòð
> ²°âò`ðä xðùôäàú´ðñq°ðbô´Ððüpðèôðpòиøqàüè
ôðñÈ0TððåyðpØôðpôÐòppñ°°rpðÐÈ
> ðõòàðð¹pôqðÒqðùôðòøøøôèðÐPðøððqòØÉÕøðñø°|ðð0°ö°à¨ÚrXðÐðòÐ
ðö2ðàØÙôðàØô°
> ¹òsðó6øtxðôð40ðqraid5.p0 len 117225472s driveoffset
> 18446744073709551615s state crashed detached
> sd name raid5.p0.s2 drive d3 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 2048s
>
> Drive /dev/ad1s1e: 55 GB (60019835904 bytes)
> Drive /dev/ad2s1e: 55 GB (60019835904 bytes)
> Drive d3: Device /dev/ad3s1e
> Created on warhol.deviantart.com at Wed Jun 14
18:19:59
> 2000
> Config last updated Wed Jun 14 18:20:35 2000
> Size: 60019835904 bytes (57239 MB)
> volume raid5 state down
> plex name raid5.p0 state down org raid5 1024s vol raid5
> sd name raid5.p0.s0 drive d1 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 0s
> sd name raid5.p0.s1 drive d2 plex ò²u!¹ðððÔÁüòÀðвðò°0ñðððàô
> h`ñÆòòð0°ðàòòÄÞpøÜðòð
> ²°âò`ðä xðùôäàú´ðñq°ðbô´Ððüpðèôðpòиøqàüè
ôðñÈ0TððåyðpØôðpôÐòppñ°°rpðÐÈ
> ðõòàðð¹pôqðÒqðùôðòøøøôèðÐPðøððqòØÉÕøðñø°|ðð0°ö°à¨ÚrXðÐðòÐ
ðö2ðàØÙôðàØô°
> ¹òsðó6øtxðôð40ðqraid5.p0 len 117225472s driveoffset
> 18446744073709551615s state crashed detached
> sd name raid5.p0.s2 drive d3 plex raid5.p0 len 117225472s driveoffset
> 265s state empty plexoffset 2048s
>
> Drive /dev/ad3s1e: 55 GB (60019835904 bytes)
>
> Any ideas?
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D11004C.F68E3B82>