← Back to team overview

kernel-packages team mailing list archive

[Bug 344631] Re: mount.ntfs-fuse not properly umounting devices?

 

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-ntfs (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ntfs in Ubuntu.
https://bugs.launchpad.net/bugs/344631

Title:
  mount.ntfs-fuse not properly umounting devices?

Status in “linux-ntfs” package in Ubuntu:
  Confirmed

Bug description:
  Trying to change a label to an ntfs partition whit ntfslabel command,
  I receive this message

  ----------------------------------------------------------------------------------------
  luca@luca-desktop:~$ sudo umount /dev/sdb1

  luca@luca-desktop:~$ sudo ntfsfix /dev/sdb1
  Mounting volume... OK
  Processing of $MFT and $MFTMirr completed successfully.
  NTFS volume version is 3.1.
  NTFS partition /dev/sdb1 was processed successfully.

  luca@luca-desktop:~$ sudo ntfslabel -v /dev/sdb1 mila
  Volume is scheduled for check.
  Please boot into Windows TWICE, or use the 'force' option.
  NOTE: If you had not scheduled check and last time accessed this volume
  using ntfsmount and shutdown system properly, then init scripts in your
  distribution are broken. Please report to your distribution developers
  (NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
  shutdown instead of proper umount.

  luca@luca-desktop:~$ 
  -----------------------------------------------------------------------------------------

  Because I didn' t schedule any check, and my windows box shutdown
  corretly the last two times, I'm  reporting this to you.

  I' m  running Ubuntu 8.10 AMD64.

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