Util-Linux package development
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: util-linux-ng@vger.kernel.org
Subject: *fdisk doesn't check 2TB boundary
Date: Thu, 7 May 2009 16:43:58 +0200	[thread overview]
Message-ID: <20090507144358.GE4661@tiehlicka.suse.cz> (raw)

[Please CC me as I am not subscribed to the list]

Hi,

we have received report from one of our customers that they have a
problem with sfdisk which doesn't check and shout loudly when 2TB
boundary is crossed when partition is created. This results in silent
ignoring of the new partition.

I have noticed a similar bug report in Debian bugzilla[1] but this one
is silent for more than 4 years.

I do understand that user should know what he is doing when creating a
partion and that msdos partitions are limited to 2TB, but is there any
special reason why this limit is not checked?

---
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=324525
-- 
Michal Hocko
L3 team 
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

                 reply	other threads:[~2009-05-07 14:43 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=20090507144358.GE4661@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=util-linux-ng@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