On Sun, Jun 07, 2015 at 07:46:43PM -0500 or thereabouts, Theodore Wynnychenko 
wrote:
> Hello
> 
> I have been trying to use the ntfs_3g fuse package to get write access to an
> ntfs drive.
> 
> While I have had no issues mounting the drive and writing to it, occasionally 
> I
> have problems when trying to unmount the drive.

I used to see something similar with 5.6-stable with a usb drive but no longer 
with 
5.7-stable. On 5.6 

# mount 

still listed the drive as mounted. 

# umount fusefs

unmounted for me perfectly well. 

Good Luck 
Moss

> 
> Basically, I want to make a more "portable" copy of my data.  I have an 
> external
> eSata drive.  The drive is NOT mounted during boot.
> 
> I have a cron job that runs a script and makes a copy of my data to the 
> external
> drive.  The script is simple:
> 
> ---
> #!/bin/sh
> /usr/local/bin/ntfs-3g /dev/sd2i /home/backup
> /usr/local/bin/rsync --recursive --archive --delete /home/data/
> /home/backup/data
> /sbin/umount /home/backup
> ---
> 
> It appears that when there aren't many new or changed files, everything is 
> fine.
> However, if there is a "lot" of new data to copy, the umount command at the 
> end
> returns an error, and the mount point for the drive is "missing."  Running the
> commands manual produces the same error.  E.g.:
> 
> # /usr/local/bin/ntfs-3g /dev/sd2i /home/backup
> << no errors >>
> # /usr/local/bin/rsync --recursive --archive --delete /home/data/
> /home/backup/data
> << no errors >>
> # /sbin/umount /home/backup
> umount: /home/backup: Device busy
> 
> But, if I check with df, the "fusefs" mounted as /home/backup is gone.
> And:
> # ls /home/backup/
> ls: /home/backup/: No such file or directory
> 
> But:
> # mkdir /home/backup
> mkdir: /home/backup: File exists
> 
> Reboot the system, and the missing mount point (/home/backup) reappears.
> 
> I was thinking that maybe this has something to do with the writing of data to
> the ntfs volume not being complete when the umount command is executed.  So, I
> did add a "sleep 600" into the shell script; and it seemed to unmount cleanly
> (although, I am not sure if it was the time delay, or just a lack of new data
> for rsync to copy).
> 
> However, that doesn't address the underlying issue.
> Also I don't understand why the mount point being used by ntfs_3g would be
> missing with "ls" but exists with "mkdir".
> I have gone through the package's man pages and could find nothing that 
> appears
> relevant.
> 
> I would appreciate any ideas on how to proceed.
> 
> Thanks
> 
> [demime 1.01d removed an attachment of type application/x-pkcs7-signature 
> which had a name of smime.p7s]

Reply via email to