Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Apr 2020 03:52:56 +0000
From:      bugzilla-noreply@freebsd.org
To:        vbox@FreeBSD.org
Subject:   maintainer-feedback requested: [Bug 245865] emulators/virtualbox-ose-additions doesn't let go of files placed on a Windows host shared folder
Message-ID:  <bug-245865-26505-sCr2YyfxWx@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-245865-26505@https.bugs.freebsd.org/bugzilla/>
References:  <bug-245865-26505@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked vbox@FreeBSD.org for
maintainer-feedback:
Bug 245865: emulators/virtualbox-ose-additions doesn't let go of files plac=
ed
on a Windows host shared folder
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245865



--- Description ---
virtualbox-ose-additions doesn't seem to want to let go of files placed on a
Windows host shared folder.=20=20

My host is Win8.1, VirtualBox is 6.1.6, my FreeBSD is 12.1-RELEASE-p3 and my
GUI in FreeBSD is Xfce 4.14.

Not sure if this is an issue with FreeBSD or Linux hosts.

Minimal steps to highlight issue:

1. Mount Windows shared folder, for example: sudo mount -t vboxvfs -w
Development ~/host
2. Go there in the file manager.
3. Right click "Create Document" -> "Empty File".
4. Then try to delete it.  It cannot be deleted.

If you try to delete the file from the command line:

$ rm dog
rm: dog: Text file busy

In fact it cannot be deleted even on the Windows host until the VM shuts do=
wn,
it's as if the file is still open for writing or something.

This issue came to light running some code that creates lock files, but when
done the code was unable to delete the lock files, leaving things in a lock=
ed
state.	Needless to say this is rather annoying.

Derived distros like FuryBSD exhibit the same problem.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245865-26505-sCr2YyfxWx>