Comment 10 for bug 349569

2009/6/15 Martin Pitt <email address hidden>

> ----- Forwarded message from David Zeuthen <email address hidden> -----
>
> Incidentally, the only problem (I think) we currently have with ntfs-3g
> is that the driver sometimes refuses to mount the file system if it was
> cleanly unmounted. The user experience is really bad; googling for it,
> it looks like this
>
> http://media.photobucket.com/image/ntfs-3g%20could%20not%
> 20mount/r3bol/ntfs.png<http://media.photobucket.com/image/ntfs-3g%20could%20not%%0A20mount/r3bol/ntfs.png>
>
> We can fix it this way
>
> a) check for this error (do a strstr() on "$Logfile indicates a clean
> shutdown" for example) when seeing an error when mounting NTFS
>
> b) use the GMountOperation to put up a dialog asking if the user wants
> to use the 'force' option
>
> c) remount with the 'force' option
>
> David
>
>
> ----- End forwarded message -----
>
> David,

This should not be an issue anymore. ntfs-3g supports "recover" and
"norecover" mount options to recover volumes with unclean journals (eg, if
they were not cleanly unmounted) since version 2009.2.1, "recover" is the
default if no option is specified, so it should make this issue go away.

Regards
Chris