[clug] ntfs-3g anyone?

Eyal Lebedinsky eyal at eyal.emu.id.au
Wed Jun 22 07:53:08 UTC 2016


I am making some progress:
- booted the win8.1 laptop into f22 (using a thumb-drive)
- attached the 4TB disk (as formatted+written on win8.1)
- did a checksum of the files
- all checksums correct

I now built the latest ntfs-3g (2016.2.22 from source) on the f19 machine (where I had
many failures) and am testing the disk again. 65% into the check and all the checksums
are correct. BTW there is 1.2TB of data, which is why it is being migrated from the
1.5TB disk to a 4TB one.

If it is all good then I will remount the disk using the old ntfs-3g to confirm that
it was the source of the problem.


On 21/06/16 18:42, Eyal Lebedinsky wrote:
> I am having issues with a 2.5" USB disk.
> 1)
> on fedora 19 I get these log messages when mounting the fs
>     ntfs-3g[13859]: Version 2013.1.13 integrated FUSE 27
>     ntfs-3g[13859]: Mounted /dev/sdj1 (Read-Write, label "Seagate-4TB", NTFS 3.1)
>     ntfs-3g[13859]: Cmdline options: rw,nodev,nosuid,uid=500,gid=500,dmask=0077,fmask=0177,uhelper=udisks2
>     ntfs-3g[13859]: Mount options: rw,nodev,nosuid,uhelper=udisks2,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdj1,blkdev,blksize=4096
>     ntfs-3g[13859]: Global ownership and permissions enforced, configuration type 1
> The mount is now accessible.
> On f22 I get
>     ntfs-3g[29109]: Version 2016.2.22 integrated FUSE 27
>     ntfs-3g[29109]: Mounted /dev/sdm1 (Read-Write, label "Seagate-4TB", NTFS 3.1)
>     ntfs-3g[29109]: Cmdline options: rw,nosuid,nodev,noexec,uid=0,gid=0,umask=077,fmask=0177,dmask=0077,user
>     ntfs-3g[29109]: Mount options: rw,nosuid,nodev,noexec,user,allow_other,nonempty,relatime,default_permissions,fsname=/dev/sdm1,blkdev,blksize=4096
>     ntfs-3g[29109]: Global ownership and permissions enforced, configuration type 1
> The mount point is not accessible, what I get is
>     $ ls -l /run/media/eyal/
>     ls: cannot access /run/media/eyal/Seagate-4TB: Transport endpoint is not connected
>     total 0
>     d????????? ? ? ? ?            ? Seagate-4TB
> If I mount manually
>     $ sudo ntfs-3g /dev/sdm1 /usb
> I see
>     ntfs-3g[29335]: Version 2016.2.22 integrated FUSE 27
>     ntfs-3g[29335]: Mounted /dev/sdm1 (Read-Write, label "Seagate-4TB", NTFS 3.1)
>     ntfs-3g[29335]: Cmdline options:
>     ntfs-3g[29335]: Mount options: allow_other,nonempty,relatime,fsname=/dev/sdm1,blkdev,blksize=4096
>     ntfs-3g[29335]: Ownership and permissions disabled, configuration type 1
>     ntfs-3g[29335]: Unmounting /dev/sdm1 (Seagate-4TB)
> The last line looks unexpected to me. Inspecting the mount fails:
>     $ ls -l /usb
>     ls: cannot access /usb: Transport endpoint is not connected
> Interestingly, no messages are logged with the following
>     $ sudo umount /usb
>     $ sudo umount /usb
>     umount: /usb: not mounted
> I searched and found no solution. Anyone using ntfs-3g?
> 2)
> Another issue, may be related, is that on f19 (where the mount is visible) I get bad data regularly.
> This is a new 4TB disk which I want to use for archival storage. Naturally I run checksum on the
> files and I am getting many files delivering bad checksums. Re-running fails a different set of files.
> There are no errors logged that I could find.
> I should mention that this disk was formatted and written to on Windows 8.1, and as such I expect the
> data on it to be in good shape. Furthermore, a failed checksum will come good next time I try the same
> file.
> --
> Eyal Lebedinsky (eyal at eyal.emu.id.au)

Eyal Lebedinsky (eyal at eyal.emu.id.au)

More information about the linux mailing list