[merge request] ntfs-3g (1:2012.1.15AR.8-2)

Bug #1118379 reported by Flames_in_Paradise
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ntfs-3g (Red Flag Midinux)
Fix Released
High
ntfs-3g (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

changelog 24Jan.2013:

   * Adding dpkg-source local-options.
   * Dropping dpkg-source compression levels.
   * Updating year in copyright file.
   * Dropping pre-wheezy versions from build-depends.
   * Updating to standards version 3.9.4.
   * Removing ntfs-3g.preinst with squeeze-to-wheezy upgrade cleanup.

derived from Debians PTS

Revision history for this message
In , Jean-Pierre (jean-pierre-redhat-bugs) wrote :

Description of problem:

When using the "fast restart" feature, Windows 8 uses cached metadata saved at previous shutdown instead of what is actually on disk. This may occur on any partition of internal disks mounted by Windows (not limited to the Windows system partition).

Version-Release number of selected component (if applicable):

All versions

How reproducible:

Nearly always.

Steps to Reproduce:
1. Work on Windows 8, then shutdown with fast restart enabled.
2. Boot into Linux through grub.
3. Create some new files on an internal partition which was mounted by Windows, and leave Linux
4. Reboot into Windows 8 and check the files created by Linux

Actual results:

The files created by Linux may be missing, and new files created on Windows may overwrite them.

Expected results:

The files created by Linux should be visible.

Additional info:

This apparently only happens when :
a) the fast restart feature of Windows 8 is enabled
b) Windows 8 is closed using the "Shut down" button (it does not happen when using the "Restart" button)
c) the dual booting into Linux is done though grub (it does not happen when booting into Linux through the Windows multiboot feature).

Starting chkdsk when entering Windows 8 drops the cached metadata and restores the state left by Linux.

The only known work around is to disable the fast restart feature (see http://jp-andre.pagesperso-orange.fr/advanced-ntfs-3g.html#windows8 )

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Jean-Pierre, since the only known workaround is to disable the fast restart feature from within Windows 8, what do you want me to do here? We can document this in our release notes, but if you can't fix it... :)

Revision history for this message
In , Jean-Pierre (jean-pierre-redhat-bugs) wrote :

Well, Tom, this was intended to have to issue documented in a place where users might look at, rather than asking you to do some special thing. I will take care of having it documented in the manual.

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Okay, thanks. :) I wasn't sure what you were asking for me to do here.

Revision history for this message
In , Ben (ben-redhat-bugs) wrote :

This has been referenced in the Fedora 18 release notes and in the Common Bugs page (https://fedoraproject.org/wiki/Common_F18_bugs#win8-fast-restart). Marking this bug closed.

Revision history for this message
In , Kamil (kamil-redhat-bugs) wrote :

I believe CANTFIX resolution is more appropriate, it says that even though we documented the issue, it still persists and we can't really do much about it. (Otherwise someone could see just the "closed fixed" status and assume this has been fixed somehow). Changing resolution and also component back to ntfs-3g.

However, I believe there could be ways to improve the situation. We could detect whether Win 8 is present on the computer, and if we mount NTFS partition in such case, we could force chkdsk to be run on the next Windows boot. That would make sure user data are not lost. The question is whether we can do this only if fast-restart feature is turned on (whether we can detect that somehow), otherwise this solution could be a bit annoying.

Another solution is that the installer could try to disable fast-restart feature if it detects Win 8 (again, if this is possible at all).

These are wild guesses, I'm not the expert here.

Revision history for this message
In , Jean-Pierre (jean-pierre-redhat-bugs) wrote :

CANTFIX if probably appropriate to mean that mounting a file system not sync'ed by Windows cannot be prevented from being dangerous (hibernation and fast restart on Windows 8 imply not sync'ed to disk).

Now, I think it is possible to detect the dangerous situations and refuse to mount with *future* ntfs-3g versions. This might still be unpleasant to users. You may apply the following couple of patches for that :

first : http://ntfs-3g.git.sourceforge.net/git/gitweb.cgi?p=ntfs-3g/ntfs-3g;a=commit;h=4d0b9163c9ef1f0cdbbf533317b291220c7fd1c7

then : http://ntfs-3g.git.sourceforge.net/git/gitweb.cgi?p=ntfs-3g/ntfs-3g;a=commit;h=559270a8f67c77a7ce51246c23d2b2837bcff0c9

I have tested these patches, and they are scheduled for next ntfs-3g release.

Revision history for this message
In , Kamil (kamil-redhat-bugs) wrote :

Jean-Pierre, that is great news. Refusing to mount is another great option how to make sure user data is safe. Ideally the high-level applications (Nautilus etc) could even display some reasonable error message.

Reopening this bug to track the progress.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ntfs-3g-2012.1.15-4.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ntfs-3g-2012.1.15-4.fc17

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ntfs-3g-2012.1.15-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ntfs-3g-2012.1.15-4.fc18

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package ntfs-3g-2012.1.15-4.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ntfs-3g-2012.1.15-4.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15452/ntfs-3g-2012.1.15-4.fc18
then log in and leave karma (feedback).

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ntfs-3g-2012.1.15-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ntfs-3g-2012.1.15-5.fc17

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ntfs-3g-2012.1.15-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ntfs-3g-2012.1.15-5.fc18

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

ntfs-3g-2012.1.15-4.fc17 has been pushed to the Fedora 17 obsolete repository. If problems still persist, please make note of it in this bug report.

description: updated
tags: added: raring
description: updated
Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

To approach this at a higher level opened bug1106257 [update request]_

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

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

---------------
ntfs-3g (1:2013.1.13-1) raring; urgency=low

  * New upstream release. (LP: #1106257)

  * Use dh_autoreconf

  * Resynchronise with Debian (LP: #1118379). Remaining changes:
    - Accept "syncio" mount option (a synonym for "sync") for compatibility
      with older versions of Ubuntu.

  * Dropped patches, applied upstream:
     - Add readonly-devices.patch: Mount read-only devices as read-only instead
       of failing.
     - ntfs-3g-junction-point-fix.patch: Return the correct type (DT_LINK) for
       NTFS Junction points, in readdir().

ntfs-3g (1:2012.1.15AR.8-2) unstable; urgency=low

  * Adding dpkg-source local-options.
  * Dropping dpkg-source compression levels.
  * Updating year in copyright file.
  * Dropping pre-wheezy versions from build-depends.
  * Updating to standards version 3.9.4.
  * Removing ntfs-3g.preinst with squeeze-to-wheezy upgrade cleanup.

ntfs-3g (1:2012.1.15AR.8-1) unstable; urgency=low

  * Merging upstream version 2012.1.15AR.8.
  * Updating rule for upstream changelog in rules target.
  * Updating local upstream changelog to upstream version 2012.1.15AR.8.

ntfs-3g (1:2012.1.15AR.7-2) unstable; urgency=low

  * Removing incomplete feature list in package long-description
    (Closes: #687054).
  * Building with unconditional multiarch support for debian-
    jessie/wheezy-backports.
  * Removing pre-wheezy transitional package.
  * Removing pre-wheezy conflicts and replaces.

ntfs-3g (1:2012.1.15AR.7-1) unstable; urgency=low

  * Merging upstream version 2012.1.15AR.7.
  * Removing readdir.patch, included upstream.

ntfs-3g (1:2012.1.15AR.6-1) unstable; urgency=low

  * Merging upstream version 2012.1.15AR.6.
  * Updating local upstream changelog.
  * Adding patch from upstream to fix the readdir syscall to set the
    d_type to 10 (Symbolic link) whenever a junction point is detected,
    avoids loops on windows 7 NTFS (Closes: #685551).
  * Protecting multiarch queries since install files are run with set -
    e.
 -- Dmitrijs Ledkovs <email address hidden> Thu, 14 Feb 2013 18:06:59 +0100

Changed in ntfs-3g (Ubuntu):
status: New → Fix Released
Changed in ntfs-3g (Red Flag Midinux):
importance: Unknown → High
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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