| 1 |
On Sunday 24 September 2006 03:56, Richard Fish wrote: |
| 2 |
> Take a look at one of the good superblocks with mdadm --examine. That |
| 3 |
> should give you an idea of what options to give to create. You'll |
| 4 |
> want to make sure you use the same layout, chunksize, etc... |
| 5 |
|
| 6 |
Luckely I wrote down the exact command I used to create the array so that |
| 7 |
part should be easy. |
| 8 |
|
| 9 |
> You should then be able to recreate the array with mdadm --create |
| 10 |
> --assume-clean, and get access to your filesystem and data. |
| 11 |
|
| 12 |
I didn't pay attention to that option before. But now I tried it. The data |
| 13 |
on that array is not that important, most have been backed up elsewhere. |
| 14 |
It seemed to work. After recreating the array I ran fsck. The filesystem |
| 15 |
is ext3. It recovered the journal and cleared 5 orphaned inode and the |
| 16 |
filesystem seemed fine. I could mount it and access the data. The array |
| 17 |
synchronized again. |
| 18 |
For safety though I might copy the data elsewhere and recreate the |
| 19 |
filesystem from scratch. |
| 20 |
|
| 21 |
-- |
| 22 |
Jesper |
| 23 |
01:17:47 up 17:42, 18 users, load average: 0.14, 0.19, 0.25 |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives