On 02/05/17 14:08, Patrik Dahlström wrote:
On 04/29/2017 11:56 AM, Andreas Klauer wrote:
On Sat, Apr 29, 2017 at 12:46:15AM +0200, Patrik Dahlström wrote:
You could create the RAID first and the overlay afterwards.
Or you can create loop devices on the busy devices and use those.
I solved it by creating loop devices and use dd. I let it finish, then
ran fsck and resize2fs on the partition and now my data is back!
Thank you all for your invaluable help!
Would it be worth it for me to write up an article on the wiki on how to
re-create messed up metadata?
Hey - I was planning to do that! :-)
Seriously, yes of course, please do. That would be wonderful. It belongs
best after "Recovering a damaged RAID" in the "When things go Wrogn"
section, i think.
Just skim the contribution guidelines before you start, they're nothing
onerous, just use good English and use "I" a lot, take responsibility
for what you write. It's meant to be easy reading but informative. A
case study of what you did would be marvelous.
I need to edit the page about that script you ran, and put a big big
warning in front of it not to run it recklessly :-)
(Contact me off-line if you haven't got an account and have difficulty
creating one.)
Cheers,
Wol
--
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
