| 1 |
Am 14.04.2011 22:19, schrieb James: |
| 2 |
> |
| 3 |
>> *Head scratch* This, uhm, looks odd. No clue what to make of it. |
| 4 |
> |
| 5 |
> Ahhh, |
| 6 |
> |
| 7 |
> Don't give up just yet? |
| 8 |
> |
| 9 |
> I issued these commands: |
| 10 |
> |
| 11 |
> mdadm --create /dev/md127 --level=1 --raid-devices=2 |
| 12 |
> --metadata=0.90 /dev/sda1 /dev/sdb1 |
| 13 |
> |
| 14 |
> mdadm --create /dev/md125 --level=1 --raid-devices=2 |
| 15 |
> --metadata=0.90 /dev/sda3 /dev/sdb3 |
| 16 |
> mdadm: /dev/sda3 appears to be part of a raid array: |
| 17 |
> level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011 |
| 18 |
> mdadm: /dev/sdb3 appears to be part of a raid array: |
| 19 |
> level=raid1 devices=2 ctime=Thu Apr 14 13:22:32 2011 |
| 20 |
> Continue creating array? y |
| 21 |
> |
| 22 |
> |
| 23 |
> mdadm --create /dev/md126 --level=1 --raid-devices=2 |
| 24 |
> --metadata=0.90 /dev/sda2 /dev/sdb2 |
| 25 |
> |
| 26 |
> I'm not sure if I just wiped the drives clean (empty)? |
| 27 |
> |
| 28 |
> If so, I'll have to start over.....? |
| 29 |
> |
| 30 |
|
| 31 |
Ouch, I didn't think of that. Well, I guess it will not wipe it, it will |
| 32 |
merely re-sync the disks. Since they have been mirrors of each other |
| 33 |
before this action, you might be lucky and it keeps working. |
| 34 |
|
| 35 |
> mdadm --detail /dev/md1 |
| 36 |
> mdadm: cannot open /dev/md1: No such file or directory |
| 37 |
> |
| 38 |
> same now for md2 and md3... |
| 39 |
> |
| 40 |
|
| 41 |
Well, at least you are rid of the duplicate arrays. |
| 42 |
|
| 43 |
> Look (ma no hands!): |
| 44 |
> |
| 45 |
> livecd gentoo # mdadm --detail /dev/md125 |
| 46 |
> /dev/md125: |
| 47 |
> Version : 0.90 |
| 48 |
> Creation Time : Thu Apr 14 14:15:21 2011 |
| 49 |
> Raid Level : raid1 |
| 50 |
> Array Size : 1948227584 (1857.97 GiB 1994.99 GB) |
| 51 |
> Used Dev Size : 1948227584 (1857.97 GiB 1994.99 GB) |
| 52 |
> Raid Devices : 2 |
| 53 |
> Total Devices : 2 |
| 54 |
> Preferred Minor : 125 |
| 55 |
> Persistence : Superblock is persistent |
| 56 |
> |
| 57 |
> Update Time : Thu Apr 14 15:51:46 2011 |
| 58 |
> State : clean, resyncing |
| 59 |
> Active Devices : 2 |
| 60 |
> Working Devices : 2 |
| 61 |
> Failed Devices : 0 |
| 62 |
> Spare Devices : 0 |
| 63 |
> |
| 64 |
> Rebuild Status : 37% complete |
| 65 |
> |
| 66 |
> UUID : fa800cdb:33955cfd:cb201669:f728008a (local to host livecd) |
| 67 |
> Events : 0.6 |
| 68 |
> |
| 69 |
> Number Major Minor RaidDevice State |
| 70 |
> 0 8 3 0 active sync /dev/sda3 |
| 71 |
> 1 8 19 1 active sync /dev/sdb3 |
| 72 |
> |
| 73 |
> |
| 74 |
[...] |
| 75 |
> We'll see in a few hours.... |
| 76 |
> |
| 77 |
> |
| 78 |
> James |
| 79 |
> |
| 80 |
|
| 81 |
You can keep using it while it re-syncs. Re-syncing just means that you |
| 82 |
do not have any redundancy, yet. You can still read/write on the array. |
| 83 |
You will get or manipulate whatever mdadm thinks is the correct value |
| 84 |
for each block. That's also what will end up on both disks, ultimately. |
| 85 |
I guess you can even reboot but since your setup is not really |
| 86 |
persistent, I wouldn't try it. |
| 87 |
|
| 88 |
Regards, |
| 89 |
Florian Philipp |
Archives