| Summary: | parted seg faults on a disk image | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Brian Brock <bbrock> | ||||
| Component: | parted | Assignee: | Brian Lane <bcl> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Release Test Team <release-test-team> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.2 | ||||||
| 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-02-03 21:39:54 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Brian Brock
2012-01-27 23:39:41 UTC
Created attachment 557978 [details]
core dumped with parted segfault
I'm running the above commands as root, against /root/disk.img I can't reproduce this. It works fine on rhel6.2 x86_64 for me. It is hitting ped_assert so there should be more text there, including a message about reporting the bug. [root@cameras ~]# dd if=/dev/zero of=disk.img bs=1k count=1k 1024+0 records in 1024+0 records out 1048576 bytes (1.0 MB) copied, 0.0233233 s, 45.0 MB/s [root@cameras ~]# parted -s disk.img mklabel gpt [root@cameras ~]# parted -s disk.img u s p Model: (file) Disk /root/disk.img: 2048s Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags Can you reproduce this on another machine or in a virt? I had a typo in my script. dd using disk.img and parted using drive.img So, the seg fault occurs on a disk image that was generated another way, or was somehow altered. For starters, it's not a sparse file. I don't think it should seg fault, but it's also not as severe as I originally thought. I'll find a reproducible case and post more info. Feel free to reopen if you can find a consistent reproducer. |