From: Karel Zak <kzak@redhat.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: util-linux@vger.kernel.org
Subject: Re: sfdisk, latest fixes break ppc64
Date: Wed, 22 Apr 2015 15:28:27 +0200 [thread overview]
Message-ID: <20150422132827.GF27969@ws.net.home> (raw)
In-Reply-To: <201504221242.18521.sweet_f_a@gmx.de>
On Wed, Apr 22, 2015 at 12:42:18PM +0200, Ruediger Meier wrote:
> On Wednesday 22 April 2015, Karel Zak wrote:
> > On Tue, Apr 21, 2015 at 12:34:26PM +0200, Ruediger Meier wrote:
> > > the latest sfdisk fixes 2928068a..a53e37f9 seem to break ppc64
> >
> > The latest changes in sfdisk only shows stupid LE/BE bugs we have in
> > GPT code. The problem should be fixed now.
>
> Most issues are fixed now so I guess 2.26.2 will be a good one :)
I hope so:-) Next time it would be nice to detect and fix such bugs
in major release or in .1 ... we need a way how to motivate users to
use -rc releases (t-shits, beers? ;-)
> There are still some random failures sometimes like this:
>
> : resize ... FAILED (sfdisk/gpt-resize)
> ....
> [ 604s] --- /home/abuild/rpmbuild/BUILD/util-linux-2.26.git233.01aa/tests/expected/sfdisk/gpt-resize 2015-04-22 06:40:45.002363998 +0000
> [ 604s] +++ /home/abuild/rpmbuild/BUILD/util-linux-2.26.git233.01aa/tests/output/sfdisk/gpt-resize 2015-04-22 10:22:27.514581956 +0000
> [ 604s] @@ -1,3 +1,4 @@
> [ 604s] +Re-reading the partition table failed.: Device or resource busy
> [ 604s] Checking that no-one is using this disk right now ... OK
> [ 604s]
> [ 604s] Disk <removed>: 50 MiB, 52428800 bytes, 102400 sectors
> [ 604s] @@ -20,4 +21,5 @@
> [ 604s]
> [ 604s] The partition table has been altered.
> [ 604s] Calling ioctl() to re-read partition table.
> [ 604s] +The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
> [ 604s] Syncing disks.
Yes, I know about it, but I'm able to reproduce this only on ppc, add
"sleep 10" to the test fixes the problem, so I guess that "udevadm
settle" is not so reliable on ppc.
Note that I'm working on new resize code, so this test will go away
and it will be replaced with separated "resize" test script.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-04-22 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 10:34 sfdisk, latest fixes break ppc64 Ruediger Meier
2015-04-22 10:13 ` Karel Zak
2015-04-22 10:42 ` Ruediger Meier
2015-04-22 13:28 ` Karel Zak [this message]
2015-04-22 14:20 ` Ruediger Meier
2015-04-22 14:50 ` Bernhard Voelker
2015-04-22 15:46 ` Karel Zak
2015-04-22 16:10 ` Ruediger Meier
2015-04-22 16:02 ` Ruediger Meier
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=20150422132827.GF27969@ws.net.home \
--to=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--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