Bug 597522

Summary: Exception error during parsing of fstab file with ntfs-3g partition FS type
Product: [Fedora] Fedora Reporter: Andrei <firehead.spb>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 13CC: anaconda-maint-list, firehead.spb, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-29 11:27:46 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:
Attachments:
Description Flags
Exception report none

Description Andrei 2010-05-29 11:25:36 UTC
Created attachment 417844 [details]
Exception report

Description of problem: i made an upgrade of F12 up to F13 with usage of 'preupgrade' tool. After downloading all required packages Linux went to reboot to continue installation of these packages. And during running of anaconda i received the following exception error: scanned format (ntfs) differs from fstab format (ntfs-3g). For more details please look at the attached file.

Steps to Reproduce:
0. i have got 'fstab' file with the following line:
---
UUID=822024B42024B159                     /mnt/win.d              ntfs-3g  defaults,noauto 0 1
---
1. there F12 64-bit Linux with the latest versions of all packages.
2. start 'preupgrade' tool and wait while it performs downloading of all required packages.
3. go to reboot
4. wait while 'anaconda' starts

Actual results: exception error: scanned format (ntfs) differs from fstab format (ntfs-3g).

Expected results: successful starting of 'anaconda'.

Additional info: if i comment this line installation will finished successfully.

Comment 1 Chris Lumens 2010-05-29 11:27:46 UTC

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