From: jmerkey <jmerkey@soleranetworks.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Swap Bug Massive EXT3 Corruption on FC4 with 2.6.14 update
Date: Thu, 17 Nov 2005 11:05:48 -0700 [thread overview]
Message-ID: <437CC67C.4060109@soleranetworks.com> (raw)
When instaling FC4 on a system which already has FC2 previously
installed on a second hard drive, the install program becomes
confused and assigns the swap partition to the FC2 system when
installing FC4. The kernel then IGNORES the size extents set
for the swap partition (in this case FC2 was set to 1024, FC4 was set to
2048) and allows the cross mounted swap to grow into
the next partition, totally corrupting the root drive (/) by allowing
the swap segment to grow into the root drive and overwrite
it.
To reproduce, install FC2 on an /dev/hda device with defaults, then
install FC4 on a /dev/hdb device, build the 2.6.14 update for
FC4 and watch your data disappear.
Jeff
next reply other threads:[~2005-11-17 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 18:05 jmerkey [this message]
2005-11-18 20:35 ` Swap Bug Massive EXT3 Corruption on FC4 with 2.6.14 update Alan Cox
2005-11-18 20:04 ` jmerkey
2005-11-18 20:13 ` jmerkey
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=437CC67C.4060109@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=linux-kernel@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