From: "simply service" <simplyservice@mobile.rogers.com>
To: martin.bene@icomedias.com, neilb@cse.unsw.edu.au,
stclists@wearesimply.com
Cc: linux-raid@vger.kernel.org
Subject: Re: AW: Raid 5 and Power Failure
Date: Sat, 13 Jul 2002 21:43:29 -0400 [thread overview]
Message-ID: <20020714014143Z315536-685+8653@vger.kernel.org> (raw)
Well, it worked...the data seems to be intact! I just mounted it r/o and the files are there...then did an interactive fsck scan and everything is in order... Thank you both...from myself and about 40 fans of japanese animation from the uao (www.otakuuniversity.org).
Jason Pfingstmann, CNA
Vice President
University of the Anime Otaku
next reply other threads:[~2002-07-14 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 1:43 simply service [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 10:01 AW: Raid 5 and Power Failure Martin Bene
2002-07-15 0:29 ` Neil Brown
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=20020714014143Z315536-685+8653@vger.kernel.org \
--to=simplyservice@mobile.rogers.com \
--cc=linux-raid@vger.kernel.org \
--cc=martin.bene@icomedias.com \
--cc=neilb@cse.unsw.edu.au \
--cc=stclists@wearesimply.com \
/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).