From: Miroslav Rovis <m.rovis@inet.hr>
To: linux-raid@vger.kernel.org
Subject: raid6 recovered, but what went wrong?
Date: Thu, 08 Mar 2012 15:57:25 +0100 [thread overview]
Message-ID: <4F58C8D5.8070907@inet.hr> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, everyone!
I have had about seven (7) days of profound musing about my data on LVM
on rai6 recovery.
It turned out to have been, rather likely, an issue with bad hardware
induced broken software raid. Linux software Raid 6.
I'm only making my conclusions due to overwhelming likelihood. I am no
expert. Just a user.
As a side interest, very much I would like to know whether my claims (on
hardware induced breakage), and there's even a video linked for that
purpose, are as probable as they seem to me.
But I wouldn't bother this list solely for that, no, pls. bear with me!
Further down as I went in my investigating of my system (there was more,
a few days earlier, but it's related to hardware known to use, and
hardware to be checked by installing it on the known good (which is the
main reason for my claim that the broken software raid is hardware
induced), and there is no need to delve into that in case that part of
my query would be rejected by the list, or ther would be no interest.
I am writing to this list predominantly related to my wish to understand
how and what exactly went wrong with the software raid, and that I
believe is clearly of interest to this list!
So, anyone who would like to give me, and possibly other readers, a tip
or two how to avoid hardware induced raid breakage, pls. have a look
from the start of this long three days worth of little sleep and doing
nothing else but recovery saga:
http://forum.cgsecurity.org/phpBB3/lvm2-on-raid6-partition-recovery-t80.html
And, the more appropriate question for the list:
what exactly went wrong with my raid6.
I almost lost nearly one quarter of my computing space, and I am oldish
and keep dozens and even hundreds of Gigabytes scattered around
belonging to different projects before I am done with them and archive them.
I managed to recover my data but I still find it hard believing that the
data is not gone.
I am greatly relieved now, and I only kept calm until now, mostly
because I didn't allow myself to contemplate on all the projects that
would be permanently lost for me if the system wasn't recovered.
I am, as well, so tired with it, that I couldn't muster my questions
more precisely at this time.
It's still been, with all the calmness, little sleep, much worry, and
hard concentrated caution, and that is a little unnerving experience.
I hope, for broaching of the matter, this could be sufficient, given
these circustances.
I could give a better query to the list in a few hours time, when I
recover myself a little better. It is a mild PTSP what would develop if
I ended up
losing months' worth of my data.
I also hope this could be of interest for the list, inasmuch as my
recovery possibly could have some points generally useful to take a look
at, for a software raid user.
Possibly.
Thank you most sincerely!
I truly hope to reach some lending ears over there!
Miroslav Rovis
Croati
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9YyNMACgkQ5NaGZVDan0pVEACfXOQvoA7j09ew0xcDGm2k8Iy4
aaUAmgIhS3CH8ze/n1Ef4Z7z/Ahbh34l
=1iS7
-----END PGP SIGNATURE-----
reply other threads:[~2012-03-08 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F58C8D5.8070907@inet.hr \
--to=m.rovis@inet.hr \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).