Bug 474282
| Summary: | ntfs-config creates fstab line with fuseblk instead of ntfs-3g | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Edward Kuns <eddie.kuns> |
| Component: | ntfs-config | Assignee: | Xavier Lamien <lxtnow> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | lxtnow |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-12-18 07:06:51 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: | |||
|
Description
Edward Kuns
2008-12-03 04:53:19 UTC
Is anyone responsible for this component? sorry, i was late on that one. will check this out hmm...
Could you perform "ntfs-config-root --debug --query-database=all" command line and upload its full output somewhere.
Currently, it just works fine from my side:
=======
fstab:
=======
#Entry for /dev/sdb1 :
UUID=EC80E28C80E25C98 /media/Lxt_-_PATA160 ntfs-3g defaults,locale=en_US.UTF-8 0 0
==============
debug data:
==============
Info for sdb1 :
-> DEV=sdb1
-> FS_DRIVERS={'all': {'ntfs-3g': ['ntfs-3g', 'Read-write driver', 0], 'ntfs': ['ntfs', 'Unknow driver', 0], 'ntfs-fuse': ['ntfs-fuse', 'Read-write driver', 0], 'auto': ['auto', 'Secondary Driver', 0]}, 'primary': [['ntfs-fuse', 'Read-write driver', 0], ['ntfs', 'Unknow driver', 0], ['ntfs-3g', 'Read-write driver', 0]], 'secondary': [['auto', 'Secondary Driver', 0]]}
-> FS_LABEL_ENC=Lxt\x20-\x20PATA160
-> PATH=pci-0000:00:1d.7-usb-0:1:1.0-scsi-0:0:0:0
-> MODEL=USB_Mass_Storage_Device
-> FS_UUID_ENC=EC80E28C80E25C98
-> FS_UUID=EC80E28C80E25C98
-> BUS=usb
-> FS_LABEL=Lxt - PATA160
-> FS_USAGE=filesystem
-> DEV_NUM=2065
-> VENDOR=Myson_Century,_Inc.
-> PARENT=sdb
-> FS_VERSION=3.1
-> FS_TYPE=ntfs
-> REMOVABLE=False
-> DEVICE=/dev/sdb1
-> SERIAL=Myson_Century,_Inc._USB_Mass_Storage_Device
-> FS_LABEL_SAFE=Lxt_-_PATA160
-> MINOR=17
-> SIZE=163921572864.0
-> MAJOR=8
-> IGNORE=False
-> SYSFS_PATH=/sys/block/sdb/sdb1
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |