File and directory removal, rename and move may have been denied with an "Operation not supported" error message

[Agostino Russo]

Binary package hint: ntfs-3g

This is confirmed on ntfs-3g website (see faq), but it seems that the release 1.2216 has a fix for that. From the changelog (thanks to Evan Dandrea for pointing that out):

"Fix: file and directory removal, rename and move may have been denied with an "Operation not supported" error message."

In particular a Wubi user reported the following error while performing a kernel upgrade in wubi (ntfs-3g) which is likely to be related to the above:

Processing triggers for initramfs-tools ...
ln: creating hard link `/boot/initrd.img-2.6.24-11-generic.dpkg-bak' => `/boot/initrd.img-2.6.24-11-generic': Operation not permitted
dpkg: subprocess post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (2)
A package failed to install. Trying to recover:
Setting up initramfs-tools (0.85eubuntu26) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-ubuntu-modules-2.6.24-11-generic (2.6.24-11.15) ...
ln: creating hard link `/boot/initrd.img-2.6.24-11-generic.dpkg-bak' => `/boot/initrd.img-2.6.24-11-generic': Operation not permitted
dpkg: error processing linux-ubuntu-modules-2.6.24-11-generic (--configure):
 subprocess post-installation script returned error exit status 1

Hence I would like to ask for a feature freeze exemption to allow for an upgrade of the ntfs-3g package to 1.2216.

[Agostino Russo (ago)]

As it turns out, the error report above was not due to ntfs-3g deficiencies, since the user was on vfat... The issue was that in hardy initrd generation involves hard links (https://wiki.ubuntu.com/HardyInitramfsErrorHandling) which are not supported by vfat.

In any case I still think that upgrading to 1.2216 makes sense since the inability to perform normal file operations in ntfs might have well generated similar (if not worse) issues.

[Martin Pitt (pitti)]

I went through the changelog since 1.1120: http://mercurial.creo.hu/repos/ntfs-3g-hg/index.cgi/shortlog/tip. Lots of bug fixes and the following new features:

 - http://mercurial.creo.hu/repos/ntfs-3g-hg/index.cgi/rev/4df9d50ae6fe (including stripped-down fuse-lite): does not apply to us, we continue to build against the system library

 - http://mercurial.creo.hu/repos/ntfs-3g-hg/index.cgi/rev/5b3df15aa4f0 (add ntfs-3g.probe): new tiny standalone program, doesn't affect other code, ok

 - http://mercurial.creo.hu/repos/ntfs-3g-hg/index.cgi/rev/85511bb4285c (support user mount via setuid root ntfs-3g (fusermount isn't required)): Add fusermount to fuse-lite, the internal fuse copy. Since we do not use that, it does not affect us.

So, approved FF exception-wise.

I'll do a merge and some tests now.

[Martin Pitt (pitti)]

I have done the merge, and performed some tests successfully:

 - copying, comparing, and reading back lots of small files
 - copying, comparing, and reading back a huge file
 - deleting above small and large files
 - copying lots of files within the NTFS partition
 - file names with UTF-8 characters
 - operation in nautilus

I consider this sufficient for uploading and more widespread testing now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ntfs-3g - 1:1.2216-1ubuntu1

---------------
ntfs-3g (1:1.2216-1ubuntu1) hardy; urgency=low

  * New upstream bug fix release. (LP: #199161)
  * Resynchronise with Debian. Remaining changes:
    - Add udeb shlibs entries for libntfs-3g23-udeb.
    - Bump debhelper build-dependency to 5.0.22 for dh_makeshlibs
      --add-udeb.
    - Create libntfs3g23-udeb and ntfs-3g-udeb.
    - Copy ntfs-3g into the initramfs. If ntfs-3g is used to mount the root
      filesystem (either directly or via a loopback mount), load the fuse
      module beforehand, and save ntfs-3g's PID (indirectly) in
      /var/run/sendsigs.omit.
    - Move ntfs-3g to /bin.
    - Move libntfs-3g.so.* to /lib. Adjust libntfs-3g.so symlink to match.
    - Add /sbin/mount.ntfs symlink to /bin/ntfs-3g.
    - Add a symlink for the mount.ntfs manual page too.
    - Pass basenames rather than full paths to pidof; create
      /dev/.initramfs/varrun if necessary (LP #150831).
    - Always add ntfs and ntfs-3g to sendsigs.omit (LP #181669).
    - Build against the external fuse libraries and add dependency on
      fuse-utils.

ntfs-3g (1:1.2216-1) unstable; urgency=low

  * New upstream release (Closes: #466161).
  * Drop /sbin/mount.ntfs-3g symlink, fixed upstream.
  * Bump library package name to match current soname.
  * Install pkgconfig file in devel package.

ntfs-3g (1:1.2129-2) unstable; urgency=low

  * Include mount.ntfs-3g again and create a symlink in /sbin
    (Closes: #464964).

ntfs-3g (1:1.2129-1) unstable; urgency=low

  * New upstream release (Closes: #463976).
  * Drop libfuse-dev build dependency and fuse-utils runtime dependency,
    ntfs-3g now includes its own "lite" fuse library.
  * Bump Standards-Version to 3.7.3.
  * Bump library package name to match current soname.
  * Run chrpath against the new ntfs-3g.probe binary.

 -- Martin Pitt <email address hidden> Fri, 07 Mar 2008 11:21:45 +0100

[Agostino Russo (ago)]

Martin thanks a lot!

[Vladimir Konkov (vladimirfx)]

I'ave same trouble.
Application: IntelliJ IDEA 7.0.3, sun-java6-jdk (6-06-0ubuntu1)
Action: save modifications to already existent file (create new file works well)
NTFS-3G version: 1:1.2216-1ubuntu2

100% reproducable

Please, suggest any workaround. I cannot switch my dev env to Ubuntu because of this bug.

[Szabolcs Szakacsits (szaka)]

http://ntfs-3g.org/support.html#compressed

[slowgenius (slowgenius)]

I'm having an "Operation not supported" problem that apparently was not fixed by the 1.2216 version of ntfs-3g.

It only affects one specific file, a directory which has the unfortunate name of "2.0.0.0__b03f5f7f11d50a3a". I can't delete it, move/rename it, or do anything else with it.