Bug 591821 - System upgrade fails when ntfs-3g partinition declared in /etc/fstab
System upgrade fails when ntfs-3g partinition declared in /etc/fstab
Status: CLOSED DUPLICATE of bug 577260
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
13
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-13 05:12 EDT by Krzysztof "Uosiu" Hajdamowicz
Modified: 2010-05-13 09:48 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-13 09:48:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Traceback from anaconda upgrade process (271.93 KB, text/plain)
2010-05-13 05:13 EDT, Krzysztof "Uosiu" Hajdamowicz
no flags Details

  None (edit)
Description Krzysztof "Uosiu" Hajdamowicz 2010-05-13 05:12:52 EDT
Description of problem:
If there is /etc/fstab entry with parinition type declared as 'ntfs-3g' anaconda fails to upgrade the system, because recognized partinition type is 'ntfs'

Version-Release number of selected component (if applicable):
Unknown, I've used preupgrade to migrate from f12 to f13

How reproducible:
Always

Steps to Reproduce:
1. make /etc/fstab entry with ntfs-3g
    [ uosiu @ samhain ] /home/uosiu > cat /etc/fstab | wklej
    http://wklej.org/id/333007/
2. Try to upgrade existing system
3.
  
Actual results:
Anaconda finds an error and quits

Expected results:
Anaconda updates the system

Additional info:
If you add a '#' at the beginning of declaration of NTFS partinition anaconda works perfectly
Comment 1 Krzysztof "Uosiu" Hajdamowicz 2010-05-13 05:13:54 EDT
Created attachment 413690 [details]
Traceback from anaconda upgrade process
Comment 2 Chris Lumens 2010-05-13 09:48:44 EDT

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

Note You need to log in before you can comment on or make changes to this bug.