Bug 1283112 - parted races with systemd-udevd [NEEDINFO]
parted races with systemd-udevd
Status: CLOSED DUPLICATE of bug 1245144
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: parted (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Brian Lane
Release Test Team
: 1283128 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2015-11-18 04:56 EST by Marius Vollmer
Modified: 2018-01-05 08:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-18 15:39:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
nkshirsa: needinfo? (bcl)

Attachments (Terms of Use)

  None (edit)
Description Marius Vollmer 2015-11-18 04:56:37 EST
Description of problem:

See https://github.com/cockpit-project/cockpit/issues/3177

Both parted and systemd-udevd tell the kernel about new partitions, and if circumstances are right, parted fails with an error message because it tries to tell the kernel about a partition that it already knows about.

This has probably been addressed in some way already, since I don't see this with parted 3.2.

Version-Release number of selected component (if applicable):

How reproducible:
'Always' when the circumstances are right, but very seldom normally.  Loading the system to about 100% CPU with "while true; do true; done" did the trick for me. 

Tell me if you want to reproduce this.
Comment 2 Marius Vollmer 2015-11-18 07:40:30 EST
*** Bug 1283128 has been marked as a duplicate of this bug. ***
Comment 3 Brian Lane 2015-11-18 15:39:37 EST
This is 'fixed' in 3.1-23 by changing parted so that it will probe using read only, and only close the r/w file descriptor when finished running.

Note that if you are calling parted multiple times from a script and not checking for device nodes to appear/disappear/whatever you will end up in the same situation. It is best to combine all the commands into a single parted call, or check for the expected changes between the calls.

*** This bug has been marked as a duplicate of bug 1245144 ***

Note You need to log in before you can comment on or make changes to this bug.