| Summary: | Incorrect fstype in /etc/fstab causes upgrade crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joachim Backes <joachim.backes> | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 15 | CC: | anaconda-maint-list, anupam_magma, jlaska, jonathan, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-11-02 17:14:31 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: |
|
||||||
Can you change your /etc/fstab so that the LABEL=vbox mount is ext3 (not ext4)? If you attempt to upgrade with that change, does it proceed without error? If I change ext4 to ext3 in /etc/fstab, the upgrade from F15-alpha to F15-tc1 is done *without any error message*, and after rebooting I can re-change ext3 into ext4, and /vbox can be mounted as etx4-partition. Kind regards Joachim Backes I suspect your partition is *really* ext3, but that mount.ext4 supports a fallback and is mounting the partition as ext3, despite being flagged as an ext4 partition. https://ext4.wiki.kernel.org/index.php/Frequently_Asked_Questions#Can_I_mount_existing_Ext3_as_Ext4.3F_And_vice_versa.3F_Similarly_from_Ext2_to_Ext4_and_its_reverse.3F Can you attach output from the following command? # tune2fs -l LABEL=vbox 1. tune2fs -l LABEL=vbox tune2fs 1.41.14 (22-Dec-2010) Filesystem volume name: vbox Last mounted on: /vbox Filesystem UUID: c524782d-08c6-40bb-a5da-177b70c25278 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 6111232 Block count: 24414775 Reserved block count: 1220738 Free blocks: 18424267 Free inodes: 6111220 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1018 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Filesystem created: Thu Jan 6 07:33:27 2011 Last mount time: Tue May 3 18:00:58 2011 Last write time: Tue May 3 18:00:58 2011 Mount count: 411 Maximum mount count: -1 Last checked: Thu Jan 6 07:33:27 2011 Check interval: 0 (<none>) Lifetime writes: 159 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: eec85aaa-ff4c-47d5-ba35-f77330d0d1aa Journal backup: inode blocks ------------------------------------------------------------------------- 2. I remember that I used already (some months ago) the tune2fs cmd for converting an ext3 partition to an ext4 partition, so I thought it's now a real ext4 partition. I now re-executed again the steps tune2fs -O extents,uninit_bg,huge_file /dev/DEV e2fsck -f /dev/DEV and I will retry to run the upgrade. Success: After re-executing tune2fs -O extents,uninit_bg,huge_file /dev/DEV e2fsck -f /dev/DEV and modifying the fstab entry to ext4 for /vbox, I can upgrade again from F15-TC1 to F15-TC1, and no error happens. Kind regards (In reply to comment #5) > Success: After re-executing > > tune2fs -O extents,uninit_bg,huge_file /dev/DEV > e2fsck -f /dev/DEV > > and modifying the fstab entry to ext4 for /vbox, I can upgrade again from > F15-TC1 to F15-TC1, and no error happens. That's good to hear, thanks for the feedback Joachim. I think we have enough information in this report to identify the root cause (partitions with incorrect fstype values in /etc/fstab). I'll leave this issue for anaconda-maint@ to determine how best to proceed. *** Bug 725295 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 649171 *** |
Created attachment 496518 [details] anaconda crash report Description of problem: I tried to update my current F15 x86_64 (installed as alpha version in March, and with all applied updates) with the F15 TC1. But immediately after booting the F15-TC1 DVD media and selecting an update of my current F15 a crash appeared, complaining about fstab inconsistencies. But my current F15 is running flawlessly. Version-Release number of selected component (if applicable): F15-TC1 How reproducible: always Steps to Reproduce: 1.Boot the install DVD 2.select upgrade method of the current F15 3. Actual results: anaconda crash Expected results: upgrade proceeds Additional info: The current F15 fstab: LABEL=/F15 / ext4 defaults 1 1 LABEL=disk2 /disk2 ext4 defaults 0 0 LABEL=tmp /tmp ext4 defaults 1 2 LABEL=SWAP swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 LABEL=vbox /vbox ext4 defaults 1 2 LABEL=SYSTEM_BACKUP /SYSTEM_BACKUP ext4 rw 1 2 LABEL=DISK2_BACKUP /DISK2_BACKUP ext4 rw 1 2 LABEL=VBOX_BACKUP /VBOX_BACKUP ext4 rw 1 2