public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Bertrand Jacquin <beber@meleeweb.net>
Cc: util-linux@vger.kernel.org
Subject: Re: sfdisk 2.20.1 --no-reread do BLKRRPART
Date: Mon, 20 May 2013 13:15:23 +0200	[thread overview]
Message-ID: <20130520111523.GB19935@x2.net.home> (raw)
In-Reply-To: <20120216201617.GD7482@lemonhead.scabb>


 Sorry for the delay :-)

On Thu, Feb 16, 2012 at 09:16:18PM +0100, Bertrand Jacquin wrote:
> When creating partitions on a destination that is not a block device,
> sfdisk do a BLKRRPART ioctl even when --no-reread option is used, but
> looking at documentation --no-reread only apply to the beginning
> process.
> 
> Would it be fine to extend that to the complete process ?

 Not sure, but I think it should be enough to don't call BLKRRPART
 ioctl for non-block devices.

>   dd if=/dev/zero of=/tmp/disk.img bs=1024 count=4032
>   strace -fF -s 1024 -e trace=ioctl \
>     sfdisk --no-reread -C2 -H32 -S63 -q -f \
>       /tmp/disk.img << EOF
> unit: sectors
> 
> part1 : start= 63, size= 3969, Id=83
> part2 : start= 4032, size= 98784, Id=83
> part3 : start= 102816, size= 22176, Id=83
> part4 : start= 124992, size= 0, Id=83
> EOF

...

> Re-reading the partition table ...
> ioctl(3, BLKRRPART, 0)                  = -1 ENOTTY (Inappropriate ioctl for device)
> BLKRRPART: Inappropriate ioctl for device

 This use case (disk images partitioning) should be fixed in the git
 tree.

 Thanks!

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-05-20 11:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 20:16 sfdisk 2.20.1 --no-reread do BLKRRPART Bertrand Jacquin
2013-05-20 11:15 ` Karel Zak [this message]
2013-05-21 13:35   ` Bertrand Jacquin

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=20130520111523.GB19935@x2.net.home \
    --to=kzak@redhat.com \
    --cc=beber@meleeweb.net \
    --cc=util-linux@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