Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 693764
Summary: | FormatDestroyError: error wiping old signatures from /dev/dasdb1: 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jan Stodola <jstodola> | ||||||||
Component: | parted | Assignee: | Brian Lane <bcl> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | rawhide | CC: | anaconda-maint-list, bcl, brueckner, dan, jonathan, kzak, rmancy, vanmeeuwen+fedora | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | s390x | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | anaconda_trace_hash:dc9be83dfe4c55f868b1730e9db4575fa98b60f55755f46ebbcda94665bb52ac | ||||||||||
Fixed In Version: | parted-2.3-10.fc15 | Doc Type: | Bug Fix | ||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2011-07-25 10:17:48 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Bug Depends On: | |||||||||||
Bug Blocks: | 467765 | ||||||||||
Attachments: |
|
Description
Jan Stodola
2011-04-05 14:27:23 UTC
Created attachment 489991 [details]
Attached traceback automatically from anaconda.
Steps to reproduce: 1. run cpfmtxa in CMS to format an DASD disk 2. start the installation in vnc mode 3. when asked, format the DASD disk to use with linux 4. create custom partitioning: /boot 500 MB swap 1000 MB / rest of the drive 5. select Next 6. traceback 10:30:21,148 INFO program: Running... wipefs -a /dev/dasdb1 10:30:21,153 ERR program: wipefs: error: /dev/dasdb1: probing initialization failed I wonder what causes that. It would be nice to call wipefs(8) with enabled debugging BLKID_DEBUG=0xffff wipefs /dev/dasdb1 note that the command without any option (e.g. -a) is not destructive ;-) The other way is call it with strace. Created attachment 490845 [details]
strace wipefs /dev/dasdb1
-bash-4.2# BLKID_DEBUG=0xffff wipefs /dev/dasdb1
wipefs: error: /dev/dasdb1: probing initialization failed
"strace wipefs /dev/dasdb1" is in the attachment
One thing is not clear to me: why is anaconda trying to wipe old signatures from /dev/dasdb1? The drive /dev/dasdb has no partitions, it was formatted before the installation using the "cpfmtxa" command in CMS and later, anaconda formatted it using dasdfmt...
-bash-4.2# ls /dev | grep dasd
dasd_eer
dasdb
(In reply to comment #5) > Created attachment 490845 [details] > strace wipefs /dev/dasdb1 open("/dev/dasdb1", O_RDONLY) = -1 ENOENT (No such file or directory) ;-) > One thing is not clear to me: why is anaconda trying to wipe old signatures > from /dev/dasdb1? The drive /dev/dasdb has no partitions, it was formatted > before the installation using the "cpfmtxa" command in CMS and later, anaconda > formatted it using dasdfmt... Maybe there is the partition, but anaconda forgot to inform kernel about the change in partition table (re-read PT ioctl, e.g. partprobe command). Reassigning back to the snake... We are wiping any old metadata from a newly created partition. The problem is that we have told parted to commit the new partition table to the disk and OS, but still the device node does not appear. This is specific to dasd devices. I have seen it several times. Adding Hendrick to CC, maybe the kernel forgets to emit some events or ... (In reply to comment #8) > Adding Hendrick to CC, maybe the kernel forgets to emit some events or ... One point could be that parted/anaconda miss the re-read partition table ioctl. On other side it might help to run udevadm settle between parted and the wipefs call. It really looks like parted doesn't issue the re-read partition ioctl or the dasds doesn't understand the partition refresh method parted is using. After writing new partition table with parted nothing happens, with fdasd the new partition is available after writing the partition table. from parted's libparted/disk.c ... /** * Tell the operating system kernel about the partition table layout * of \p disk. * * This is rather loosely defined: for example, on old versions of Linux, * it simply calls the BLKRRPART ioctl, which tells the kernel to * reread the partition table. On newer versions (2.4.x), it will * use the new blkpg interface to tell Linux where each partition * starts/ends, etc. In this case, Linux does not need to have support for * a specific type of partition table. * * \return 0 on failure, 1 otherwise. */ int ped_disk_commit_to_os (PedDisk* disk) same bug as #651478, the patch used in F-14 was missing in the F-15 package Thanks. This patch made it into upstream so rawhide has it and should work just fine. parted-2.3-10.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/parted-2.3-10.fc15 parted-2.3-10.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. Created attachment 530899 [details]
Attached traceback automatically from anaconda.
|