Hello,
I have a problem recovering a Vinum raid5 stripeset, and it was
recommended that I post the problem here.
Basically, I created a Raid5 Stripeset:
drive ibm120ad2 device /dev/ad2s1e
drive ibm120ad5 device /dev/ad5s1e
drive ibm120ad7 device /dev/ad7s1e
volume raid5
plex org raid5 512k
sd length 0s drive ibm120ad2
sd length 0s drive ibm120ad5
sd length 0s drive ibm120ad7
I ran saveconfig, to save the configuration to disk. I then proceeded to
move quite a lot of data onto the raid5 volume.
Then some time later, I reinstalled FreeBSD. To restore the raid5
volume, I ran:
read disk /dev/ad2s1e /dev/ad5s1e /dev/ad7s1e
Upon doing a list, it gives:
vinum -> list
3 drives:
D ibm120ad2 State: up Device /dev/ad2s1es1a Avail:
117796/117796 MB (100%)
D ibm120ad5 State: up Device /dev/ad5s1es1a Avail:
0/117796 MB (0%)
D ibm120ad7 State: up Device /dev/ad7s1es1a Avail:
117796/117796 MB (100%)
D *invalid* State: referenced Device Avail: 0/0 MB
1 volumes:
V raid5 State: up Plexes: 1 Size: 230
GB
1 plexes:
P raid5.p0 R5 State: corrupt Subdisks: 3 Size: 230
GB
3 subdisks:
S raid5.p0.s0 State: up PO: 0 B Size: 115
GB
S raid5.p0.s1 State: stale PO: 512 kB Size: 115
GB
S raid5.p0.s2 State: stale PO: 1024 kB Size: 115
GB
Subdisk s0 shows as present:
vinum -> list -V raid5.p0.s0
Subdisk raid5.p0.s0:
Size: 123518582784 bytes (117796 MB)
State: up
Plex raid5.p0 at offset 0 (0 B)
Drive ibm120ad5 (/dev/ad5s1es1a) at offset 135680 (132
kB)
However subdisks s1 and s2 show as missing:
vinum -> list -V raid5.p0.s1
Subdisk raid5.p0.s1:
Size: 123518582784 bytes (117796 MB)
State: stale
Plex raid5.p0 at offset 524288 (512 kB)
Drive *invalid* (*missing*) at offset 135680 (132 kB)
vinum -> list -V raid5.p0.s2
Subdisk raid5.p0.s2:
Size: 123518582784 bytes (117796 MB)
State: stale
Plex raid5.p0 at offset 1048576 (1024 kB)
Drive *invalid* (*missing*) at offset 135680 (132 kB)
They seem to have lost their drivename, so don't know which drive
represents them.
I have tried doing various things, such as changing the read disk
options, ie "read disk /dev/ad2" etc, but all had pretty much the same
result.
I am at a loss for what to do next. Initially I did attempt to mount the
raid5 volume, doing an ls on the mount point showed the correct
directories, however when I attempted to cd and then ls into them, the
kernel paniced. I since haven't been able to mount the raid5 volume, I
get "mount: /dev/vinum/raid5 on /raid5: incorrect super block". I am
concerned that I have somehow damaged the stripeset.
Unfortunately backup media for backing up 240Gb's worth of data is
rather expensive compared to how cheap disks are at the moment, and as
such I only have backups of the critical data, so any help will be
greatly appreciated!
Many thanks.
Regards,
Alasdair Lumsden
[EMAIL PROTECTED]
Here is some additional technical information: info + list -V:
vinum -> info
Flags: 0x80204
Total of 12 blocks malloced, total memory: 12432
Maximum allocs: 15, malloc table at 0xc24483a0
0 requests active, maximum 1 active
vinum -> list -V
3 drives:
Drive ibm120ad2: Device /dev/ad2s1es1a
Created on dogbert.dilbert.dns at Wed Oct 2 15:49:36
2002
Config last updated Thu Oct 3 16:34:02 2002
Size: 123518997504 bytes (117796 MB)
Used: 135680 bytes (0 MB)
Available: 123518861824 bytes (117796 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 0
Free list contains 1 entries:
Offset Size
265 241247777
Drive ibm120ad5: Device /dev/ad5s1es1a
Created on dogbert.dilbert.dns at Wed Oct 2 15:49:36
2002
Config last updated Thu Oct 3 16:34:02 2002
Size: 123518997504 bytes (117796 MB)
Used: 123518718464 bytes (117796 MB)
Available: 279040 bytes (0 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 1
Free list contains 1 entries:
Offset Size
241247497 545
Drive ibm120ad7: Device /dev/ad7s1es1a
Created on dogbert.dilbert.dns at Wed Oct 2 15:47:14
2002
Config last updated Thu Oct 3 16:34:02 2002
Size: 123518997504 bytes (117796 MB)
Used: 135680 bytes (0 MB)
Available: 123518861824 bytes (117796 MB)
State: up
Last error: none
Active requests: 0
Maximum active: 0
Free list contains 1 entries:
Offset Size
265 241247777
Drive *invalid*: Device
Created on at Thu Jan 1 01:00:00 1970
Config last updated Thu Jan 1 01: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
Free list contains 0 entries:
Offset Size
1 volumes:
Volume raid5: Size: 247037165568 bytes (235593 MB)
State: up
Flags:
1 plexes
Read policy: round robin
Plex 0: raid5.p0 (raid5), 230 GB
1 plexes:
Plex raid5.p0: Size: 247037165568 bytes (235593 MB)
Subdisks: 3
State: corrupt
Organization: raid5 Stripe size: 512 kB
Part of volume raid5
Subdisk 0: raid5.p0.s0
state: up size 123518582784 (117796 MB)
Subdisk 1: raid5.p0.s1
state: stale size 123518582784 (117796 MB)
Subdisk 2: raid5.p0.s2
state: stale size 123518582784 (117796 MB)
3 subdisks:
Subdisk raid5.p0.s0:
Size: 123518582784 bytes (117796 MB)
State: up
Plex raid5.p0 at offset 0 (0 B)
Drive ibm120ad5 (/dev/ad5s1es1a) at offset 135680 (132
kB)
Subdisk raid5.p0.s1:
Size: 123518582784 bytes (117796 MB)
State: stale
Plex raid5.p0 at offset 524288 (512 kB)
Drive *invalid* (*missing*) at offset 135680 (132 kB)
Subdisk raid5.p0.s2:
Size: 123518582784 bytes (117796 MB)
State: stale
Plex raid5.p0 at offset 1048576 (1024 kB)
Drive *invalid* (*missing*) at offset 135680 (132 kB)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
