From: Phillip Susi <psusi@cfl.rr.com>
To: Karel Zak <kzak@redhat.com>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Extended partition mapping wrong size
Date: Tue, 6 Apr 2010 12:06:55 -0400 [thread overview]
Message-ID: <4BBB5C1F.5060407@cfl.rr.com> (raw)
In-Reply-To: <20100406153348.GE7858@nb.net.home>
On 4/6/2010 11:33 AM, Karel Zak wrote:
> You have to care about the partition table (EBR).
>
> The current 1024 bytes is completely useless size, if you enlarge the
> size of the partition (for example to 1MiB) you will see reports from
> people who lost their extended partitions. (I don't believe that all
> mkfs programs are able to detect/skip EBR.)
Good point... mke2fs won't damage it since it leaves the first sector
intact and places its boot sector in sector 1 ( or was it 2? ), but FAT
and NTFS won't be so kind.
>> Then again, I could swear that once upon a time the kernel simply
>> did not bother creating a dev node for the extended partition, and
>> this seems to be a hack that was put in to make it easy for LILO to
>> install to one. Personally I'd prefer going back to the old
>> behavior of just not having a useless device there.
>
> This is probably better idea than enlarge the size :-)
Aye, I'd prefer the useless device to be removed, but at the very least
it should not use a size of 2 when the second sector is not actually
there because it is the first sector of the logical partition, though we
just patched parted to reserve that second sector anyhow even though you
are using none alignment mode, just to avoid running into this problem.
prev parent reply other threads:[~2010-04-06 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:11 Extended partition mapping wrong size Phillip Susi
2010-04-06 11:47 ` Karel Zak
2010-04-06 13:58 ` Phillip Susi
2010-04-06 15:33 ` Karel Zak
2010-04-06 16:06 ` Phillip Susi [this message]
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=4BBB5C1F.5060407@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=kzak@redhat.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