From: Dan Christensen <jdc@uwo.ca>
To: linux-raid@vger.kernel.org
Subject: recovery from mkswap on mounted raid1 ext3 filesystem?
Date: Mon, 15 May 2006 22:19:09 -0400 [thread overview]
Message-ID: <87hd3qu2xu.fsf@uwo.ca> (raw)
I accidentally ran mkswap on an md raid1 device which had a mounted
ext3 filesystem on it. I also did a swapon, but I don't think
anything was written to swap before I noticed the mistake. How much
of the partition is toast, and is it something e2fsck might fix?
Luckily I have a recent full backup, but it would be easier if
there was a quick fix! :-)
Thanks,
Dan
(For the curious: I made the mistake because my fstab file had md0 and
md1 reversed, because a few kernel revisions back the kernel decided
to name them differently. And for some reason, the "mount" command
reports the wrong information from my fstab rather than the right
information which is (for example) in /proc/mounts. Is this a bug?
Moreover, shouldn't the mkswap command check whether a device is in
use before overwriting it?
I realize this isn't the right list for these questions...)
next reply other threads:[~2006-05-16 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 2:19 Dan Christensen [this message]
2006-05-16 2:41 ` recovery from mkswap on mounted raid1 ext3 filesystem? Neil Brown
2006-05-16 3:22 ` Dan Christensen
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=87hd3qu2xu.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).