552567 – convert ntfs to ntfs-3g in fstab

Bug 552567 - convert ntfs to ntfs-3g in fstab

Summary: convert ntfs to ntfs-3g in fstab

Status:	RESOLVED DUPLICATE of bug 544199

Alias:	None

Product:	openSUSE 11.2
Classification:	openSUSE
Component:	Basesystem (show other bugs)
Version:	Final
Hardware:	x86-64 Other

Priority:	P3 - Medium Severity: Normal (vote)
Target Milestone:	---
Assignee:	Petr Uzel
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2009-11-04 17:04 UTC by Harald Koenig
Modified:	2010-07-09 11:24 UTC (History)
CC List:	4 users (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Harald Koenig 2009-11-04 17:04:58 UTC

I updated from 11.1 to 11.2 RC1 (via DVD) and further. 

now I noticed that my fstab entry 


    /dev/sda4            /windows/vista       ntfs     noauto

does not work anymore, because "ntfs" now is spelled "ntfs-3g"


IMHO the update should convert the fstype field when updating...

Comment 1 Arvin Schnell 2009-11-09 11:51:06 UTC

Simply using mount without a fstype option does not work. The mount
command should be able to use ntfs-3g instead of ntfs.

Comment 2 Arvin Schnell 2009-11-09 12:01:28 UTC

Overall the situation is inconsistent: blkid reports "ntfs" but mount
cannot use that fstype.

Comment 3 Arvin Schnell 2009-11-16 14:54:10 UTC

Also, since we support update via "zypper dup" any conversion cannot
be done by YaST but must be done by some appropriate package.

Comment 4 Stephan Kulow 2009-11-17 16:24:11 UTC

No, we support "zypper dup", but that doesn't mean it has to be feature compatible with yast update. If you need a wiki page with instructions to "polish" the update, it's fine.

Comment 8 Petr Uzel 2010-07-09 11:24:23 UTC

The root cause is missing /sbin/mount.ntfs symlink - already fixed in bug#544199.

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