Ubuntu
ntfs-3g package

Copying large folders on NTFS partition fails with "Transport endpoint is not connected"

Bug #1061874 reported by random
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ntfs-3g (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I used "ubuntu-bug storage" and chose "No permission to access files" because "Other problem" did not result in a bug report. So I am not sure if the package is correct.

I have an automounted internal partition (NTFS) which I work on the whole time. The bug is reproducable when I try to copy large directories.

1. Open console
2. Copy large directory with "cp dir dir-backup"
3. What should happen: It should copy the files. What happens: It runs a while, than it stops with the same output for some files:
"cp: writing `file.xyz': Transport endpoint is not connected"
4. Afterwards the complete partition is not accessible. When I try to open it with nautilus, I get the same message:
"Could not display "media/data". Error: Error when getting information for file '/media/data': Transport endpoint is not connected
Please select another viewer and try again."

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: udisks2 1.99.0+git20120919-1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CustomUdevRuleFiles: 86-hpmud-hp_laserjet_1018.rules 86-hpmud-hp_laserjet_p1006.rules 86-hpmud-hp_laserjet_1005_series.rules 86-hpmud-hp_laserjet_professional_p1102.rules 86-hpmud-hp_laserjet_p1005.rules 86-hpmud-hp_laserjet_p1505.rules 86-hpmud-hp_laserjet_professional_p1102w.rules 86-hpmud-hp_laserjet_professional_p1566.rules 86-hpmud-hp_laserjet_1020.rules 86-hpmud-hp_laserjet_p1007.rules 86-hpmud-hp_laserjet_p1008.rules 86-hpmud-hp_laserjet_1000.rules
Date: Thu Oct 4 22:28:48 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
MachineType: Hewlett-Packard HP EliteBook 8440p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=d72e5444-4b51-4a37-b6fb-bdbc5d03d741 ro quiet splash vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: Upgraded to quantal on 2012-09-07 (27 days ago)
dmi.bios.date: 07/14/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CCU Ver. F.0D
dmi.board.name: 172B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 30.2E
dmi.chassis.asset.tag: CZC034325L
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.0D:bd07/14/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172B:rvrKBCVersion30.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8440p
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
random (guardacaso) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Tentatively assigning to ntfs-3g. udisks has noting to do with file access.

affects: udisks2 (Ubuntu) → ntfs-3g (Ubuntu)
Revision history for this message
random (guardacaso) wrote :

The same happened when I was executing "git stash" on a git repository on that partition. In this case Ubuntu asked me to send a bug report and the suggested bug looked like a duplicate of this bug: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1019806

Revision history for this message
random (guardacaso) wrote :

This is related to the /etc/fstab file. The line for this partition looks like this:

# <file system> <mount point> <type> <options> <dump> <pass>
UUID=B63AA142792C2BD1 /media/data ntfs uid=1000,gid=1000,umask=022,exec 0 2

I commented the line out, restarted the system and mounted the partition with "sudo mount /dev/sda7 /media/data".
Afterwards I could copy the folder without problems. Did I do something wrong in the fstab line?

Revision history for this message
Jean-Pierre (jean-pierre-andre) wrote :

Please upgrade fuse. Fuse 2.9.0 has a random bug, when remounting manually you were just lucky. I would also recommend doing a chkdsk.

Revision history for this message
Jean-Pierre (jean-pierre-andre) wrote :

Oh, and I forgot to suggest replacing the final "2" in your /etc/fstab entry by "0". The value "2" is a request to make a file system check before mounting.... but AFAIK nobody has released an open source ntfs file system checker, this is just giving you a false impression of safety.

Revision history for this message
random (guardacaso) wrote :

Thank you! You were right, the bug was not gone before, but after an upgrade I can run all the operations that resulted in that bug, so I guess it is fixed.

Revision history for this message
random (guardacaso) wrote :

No it seems I just had luck again, the error still occurs. I will check my partition and perhaps switch to ext3/ext4..

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ntfs-3g (Ubuntu):
status: New → Confirmed
Revision history for this message
Christoph Buchner (bilderbuchi) wrote :

I guess it's possible that this is the same bug as #1072270, where they say this is fixed by fuse 2.9.2 in arch, so packaging/installing fuse 2.9.2. for ubuntu could resolve the problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.