From: Martin Pool <mbp@sourcefrog.net>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: rescan partitions returns EIO since 2.6.8
Date: Mon, 6 Dec 2004 11:47:22 +1100 [thread overview]
Message-ID: <20041206004722.GD26060@hp.com> (raw)
In-Reply-To: <200412051403.iB5E3EJ01749@apps.cwi.nl>
On 5 Dec 2004, Andries.Brouwer@cwi.nl wrote:
> Martin Pool changed the behaviour of the BLKRRPART ioctl in 2.6.8.
> The effect is that one now gets an I/O error when first
> partitioning an empty disk:
> # sfdisk /dev/sda
> Checking that no-one is using this disk right now ...
> BLKRRPART: Input/output error
To me it seems more correct that a request to read the partition table
should fail if the partition table can't be read. I had some code
that did care to know the difference, but if you really want to roll
it back I won't object.
fdisk, cfdisk and parted all just give a warning in this case. You
can tell sfdisk to ignore the error with --no-reread.
--
Martin
next prev parent reply other threads:[~2004-12-06 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 14:03 rescan partitions returns EIO since 2.6.8 Andries.Brouwer
2004-12-06 0:47 ` Martin Pool [this message]
2004-12-06 1:50 ` Andries Brouwer
2004-12-14 6:31 ` Martin Pool
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=20041206004722.GD26060@hp.com \
--to=mbp@sourcefrog.net \
--cc=Andries.Brouwer@cwi.nl \
--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