Through the re-creation of the array, metadata has been fixed and the
array is now as good as it was before the little accident. You can
configure auto-assembly of the array as usual in mdadm.conf (updating
the UUID is probably all you need to do). Also, you can now add the
spare disk with your standard mdadm.
Am 20.06.2012 15:54, schrieb freeone3000:
Thanks a lot for your help. I have my data back! Played a few movie
files off of the mounted drive, and they all worked perfect. Sorry for
being such a dunce with the block sizes.
`/dev/sdc3:2048s /dev/sdb3:2048s /dev/sde:2048s /dev/sdd3:1024s
missing` mounted the drive successfully. Now, is there a way to
"normalize" my drives so I can mount it without running through this
guesswork again? Or that I can re-create my array using a standard
mdadm?
On Wed, Jun 13, 2012 at 1:49 PM, Piergiorgio Sartor
<piergiorgio.sartor@xxxxxxxx> wrote:
Hi all,
On Wed, Jun 13, 2012 at 08:22:02PM +0200, Pierre Beck wrote:
I wonder if LVM activation can be done without writing to the array?
IIRC it updates at least some timestamp ...
we tried setting the array itself read only,
which prevent (or it should) anybody above,
filesystem or LVM, to perform writes...
Neveretheless, the result was a bit "strange",
namely a kernel BUG() or similar, we had to
reset the PC.
I'm not sure if this was caused by other issue,
since the PC was in a not really healty state,
or a direct consequence of md device in r/o.
bye,
--
piergiorgio
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
James Moore
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
