File and directory removal, rename and move may have been denied with an "Operation not supported" error message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wubi |
Fix Released
|
Undecided
|
Unassigned | ||
ntfs-3g (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt |
Bug Description
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/
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-
ln: creating hard link `/boot/
dpkg: error processing linux-ubuntu-
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.
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/HardyInitra mfsErrorHandlin g) 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.