Bug 744836

Summary: RHEL 5 - fdisk and parted bug?
Product: Red Hat Enterprise Linux 5 Reporter: allan.concejo
Component: partedAssignee: Brian Lane <bcl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-30 20:41:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description allan.concejo 2011-10-10 15:42:27 UTC 
Description of problem:

I'm getting inconsistent results when using parted to create/remove partitions on a USB drive.
parted seems to work fine after running fdisk to remove partitions on the USB. Sometimes however, parted would run successfully, but the partition won't show up in fdisk. Other times, it would prompt for partition type, although fat16 was already included in the options. Any feedback will be appreciated.


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

How reproducible:
parted -s /dev/sdb mkpart primary fat16 0 500 toggle 1 boot
This works after you run fdisk to remove a partition and save changes.
if you remove a partition using parted, then recreate that partition, it prompts for partition type, although 'fat16' is already included in the option.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Intermittent results. 

Expected results:


Additional info:
Comment 1 Brian Lane 2011-10-10 16:10:04 UTC 
Can you reproduce this consistently? A couple things to try:

erase the usb with dd if=/dev/zero of=device bs=1M count=1
then run parted on it a couple times. You might also try partprobe to make sure the kernel picks up the changes (although that really shouldn't be needed).

Can you reproduce it with a disk image and not a real usb device?