[Bug 906117] Re: NTFS partition unusable after copying network folder to it.

[BertN45]

On 12/20/2011 03:45 PM, Bert Nijhof wrote:
Hi again

I have tried to use the same partition on an old laptop that runs 
Lubuntu 11.10. That laptop has not been updated the last week and that 
laptop handles the ntfs partition correctly. So the problem has been 
introduced by a recent update or is in the part, which is different 
between the distros. I will update Lubuntu and see what happens.

Lubuntu handles the ntfs partition correctly also after the update, so 
the problem is probably related to the difference in speed implementing 
the updates. Remember that say a week ago also Ubuntu 11.10 handled the 
ntfs partition correctly.

I probably have to withdraw the bug report on rsync.

Good luck again

Bert

> Hi
>
> I used a similar disk and ntfs partition from my desktop (defect power 
> supply) and put it in an usb case.
>
> I think here we have the problem in the middle part of the listing. It 
> looks like the partition is rw for owner and group (same user as 
> owner). The mount command despite the umask=000 still mounts the disk 
> read only. Which is the same what happened using the Storage Device 
> Manager (gui for udisks) on the local disk a few days ago. I also 
> remember that I did correct the permissions using Windows, again using 
> an usb case. Note that on all systems I use the same user-id.
>
> Just a thought: Maybe it has nothing to do with rsync, has there been 
> an ntfs related update the last couple of days?
>
> Good luck
>
> Bert
>
> root at Dell-Ubuntu:~#
> root at Dell-Ubuntu:~# mount -l
> /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> fusectl on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> udev on /dev type devtmpfs (rw,mode=0755)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
> none on /run/shm type tmpfs (rw,nosuid,nodev)
> /dev/sda3 on /media/Dell-Data type ext4 (rw,commit=0) [Dell-Data]
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
> (rw,noexec,nosuid,nodev)
> gvfs-fuse-daemon on /home/bertadmin/.gvfs type fuse.gvfs-fuse-daemon 
> (rw,nosuid,nodev,user=bertadmin)
>
> root at Dell-Ubuntu:~# ls -l /dev/sdb2
> brw-rw---- 1 root disk 8, 18 2011-12-20 13:19 /dev/sdb2
> root at Dell-Ubuntu:~# mount -t ntfs -o umask=000 /dev/sdb2 /media/sdb2
> mount: warning: /media/sdb2 seems to be mounted read-only.
> root at Dell-Ubuntu:~# ls -l /dev/sdb2
> brw-rw---- 1 root disk 8, 18 2011-12-20 13:19 /dev/sdb2
>
> root at Dell-Ubuntu:~# mount -l
> /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
> fusectl on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> udev on /dev type devtmpfs (rw,mode=0755)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
> none on /run/shm type tmpfs (rw,nosuid,nodev)
> /dev/sda3 on /media/Dell-Data type ext4 (rw,commit=0) [Dell-Data]
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc 
> (rw,noexec,nosuid,nodev)
> gvfs-fuse-daemon on /home/bertadmin/.gvfs type fuse.gvfs-fuse-daemon 
> (rw,nosuid,nodev,user=bertadmin)
> /dev/sdb2 on /media/sdb2 type ntfs (ro,umask=000) [HP Data]
> root at Dell-Ubuntu:~#
>
>
>
>
>
>
>
>
>
>
>
>
> On 12/20/2011 04:16 AM, Jean-Pierre wrote:
>>> How is a normal user supposed to know that we have to use a
>>> special mount command in that case? If the mount has been
>>> inconsistent with rsync operation I expect a warning and not
>>> this type of own, unexpected default action of the system.
>> Your device was probably mounted automatically by udisks, which forces
>> "fmask=177, dmask=077"
>>
>>> I have used the mount command with the permission set to 777,
>>> without any success.
>> Please post your exact command, or try :
>>
>> mount -t ntfs -o permissions MY-DEVICE MY-MOUNT-POINT
>> chmod 731 MY-MOUNT-POINT/my-file
>> ls -l MY-MOUNT-POINT/my-file
>>
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ntfs-3g in Ubuntu.
https://bugs.launchpad.net/bugs/906117

Title:
  NTFS partition unusable after copying network folder to it.

Status in “ntfs-3g” package in Ubuntu:
  New

Bug description:
  I had a working ntfs partition and used it for ubuntu
  9.10/10.04/10.10/11.04 and 11.10. I had a windows XP network folder
  with full permissions set to "system" and my user-id. I used grsync to
  copy that a subfolder from the network folder to my ntfs partition.
  unfortunately it had the preserve owner, preserve group and preserve
  permission ticked.

  After the grsync operation my ntfs partition had the following
  permission settings: owner "root" with permissions to "access files"
  only. Group and Others had no permissions at all.

  It has been impossible to correct the situation manually. If grsync or
  other programs are allowed to mess up my permission, I need at least
  the possibility to manually correct it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/906117/+subscriptions