Automatic mounting of read only ntfs partition on usb device fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Medium
|
Unassigned | ||
Precise |
Fix Released
|
Medium
|
Ming Lei | ||
udisks |
Confirmed
|
Medium
|
|||
ntfs-3g (Debian) |
Fix Released
|
Unknown
|
|||
ntfs-3g (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Martin Pitt | ||
udisks (Ubuntu) |
Invalid
|
Medium
|
Ming Lei | ||
Precise |
Won't Fix
|
Medium
|
Unassigned | ||
Quantal |
Invalid
|
Medium
|
Ming Lei | ||
udisks2 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Quantal |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
OEM customers raise this issue, thinking that the error message can be misleading to inexperienced users.
[Fix]
See attachment and merge proposals.
[Test Case]
Format a SD card with NTFS, lock the SD card as write-protected, insert the card into the SD card slot. If the card is mounted as read-only, the bug is fixed.
[Regression Potential]
To ensure the patch does not cause mounting to fail completely or mounting of writable devices as readonly, verification should include both writable and readonly NTFS partitions.
[Regression testing]
The udisks2 test suite covers both read-only and writable NTFS partitions:
http://
You can download it and run it against the installed system binaries; it will use scsi-debug for a virtual hard disk/CD-ROM, and not touch any of your real partitions.
With the current versions in the archive, you get:
=======
ERROR: test_ntfs (__main__.FS)
fs: NTFS
-------
Traceback (most recent call last):
File "src/tests/
self.
File "src/tests/
self.
File "src/tests/
mount_path = cd_fs.call_
File "/usr/lib/
return info.invoke(*args, **kwargs)
gi._glib.GError: GDBus.Error:
mounting /dev/sr1 at /media/
"ntfs" -o "uhelper=
"/dev/sr1" "/media/
Error opening '/dev/sr1': Read-only file system
Failed to mount '/dev/sr1': Read-only file system
With the proposed version, the test succeeds.
If you prefer, you can also run the steps manually; described in http://
[Original Report]
Mounting of read only NTFS filesystem gives a following error popup:
Cannot mount volume.
Unable to mount the volume '<Volume name>'.
Details:
Error opening '/dev/sdb2': Read-only file system
Failed to mount '/dev/sdb2': Read-only file system
I believe this should be mounted as read-only instead of an error message.
Mounting by hand with the "-o ro" argument works as expected.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
NonfreeKernelMo
Package: mountall 2.15
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video
Related branches
- Martin Pitt: Disapprove
- Jamie Strandboge: Needs Fixing
-
Diff: 51 lines (+17/-0)1 file modifiedsrc/device.c (+17/-0)
- Martin Pitt: Disapprove
-
Diff: 5256 lines (+747/-906)22 files modifieddebian/changelog (+5/-12)
debian/control (+1/-2)
debian/local/apport-hook.py (+2/-2)
doc/html/Adapter.html (+16/-16)
doc/html/Device.html (+233/-233)
doc/html/Expander.html (+17/-17)
doc/html/Port.html (+15/-15)
doc/html/UDisks.html (+82/-82)
doc/html/index.html (+3/-3)
doc/html/ix01.html (+236/-236)
doc/html/license.html (+2/-2)
doc/html/ref-dbus.html (+2/-2)
doc/html/tools-fileformats.html (+2/-2)
doc/html/udisks-daemon.8.html (+7/-7)
doc/html/udisks-tcp-bridge.1.html (+6/-6)
doc/html/udisks.1.html (+7/-7)
doc/html/udisks.7.html (+10/-10)
doc/html/udisks.devhelp (+0/-250)
policy/org.freedesktop.udisks.policy (+82/-0)
src/device.c (+17/-0)
src/marshal.c (+1/-1)
tools/udisks-marshal.c (+1/-1)
tags: | added: blocks-hwcert-enablement |
affects: | mountall (Ubuntu) → udisks2 (Ubuntu) |
Changed in oem-priority: | |
importance: | Undecided → Medium |
Changed in udisks2 (Ubuntu): | |
assignee: | nobody → Ming Lei (tom-leiming) |
tags: | added: patch |
Changed in oem-priority: | |
status: | New → In Progress |
Changed in udisks: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in udisks (Ubuntu Precise): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in udisks2 (Ubuntu Precise): | |
status: | New → Confirmed |
description: | updated |
tags: | added: rls-q-incoming |
no longer affects: | udisks2 (Ubuntu Precise) |
Changed in udisks (Ubuntu Quantal): | |
status: | Confirmed → Invalid |
description: | updated |
description: | updated |
Changed in ntfs-3g (Debian): | |
status: | Unknown → New |
description: | updated |
description: | updated |
tags: | removed: rls-q-incoming verification-needed |
Changed in ntfs-3g (Debian): | |
status: | New → Fix Released |
Changed in oem-priority: | |
status: | Incomplete → Fix Released |
Hello Crazyguy
is this issue present with the latest lucid packages?
Thanks