Ticket #8761 (new defect)
Silent failure to delete files on Shared Folders
|Reported by:||macrovita-erw||Owned by:|
When running bonnie++ bechmark on Linux guest (Fedora 14) in a shared folder under Windows XP host, the benchmark fails due to "directory not empty" at the end.
The benchmark creates thousands of small files, and then deletes them. The problem is that after all deletions are done (and no error is reported), the benchmark directory is not empty.
Running the same benchmark on the same guest, but on a Linux native folder (VDI disk), the benchmark runs OK. No files left over.
VirtualBox 4.0.6 (the problem also occurred on VirtualBox 4.0.4, I just hadn't reported it yet, sorry)
Host: Windows XP Professional SP3
Guest: Fedora 14 kernel 18.104.22.168-83.fc14.i686
# cd /media/sf_some_shared_folder # bonnie++ -u root -n 3 -s 0 Using uid:0, gid:0. Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty Cleaning up test directory after error. # ls Bonnie.1733 # ls Bonnie.1733/ | wc -l 1106 # for i in `seq 1 5`; do bonnie++ -u root -n 3 -s 0; done Using uid:0, gid:0. Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Directory not empty Cleaning up test directory after error. ...[snip, cut 4x repeated output]... # for dir in `ls -d Bonnie*`; do \ echo -n "files left over in $dir: "; \ ls $dir | wc -l; done files left over in Bonnie.1733: 1106 files left over in Bonnie.1743: 1111 files left over in Bonnie.1744: 1102 files left over in Bonnie.1745: 1102 files left over in Bonnie.1746: 1102 files left over in Bonnie.1747: 1108 # rm -rf Bonnie.* # ls
- bonnie++ option [-n 3] creates 3 * 1024 files
- The command [rm -rf Bonnie.*] successfully deletes all left over files. That said, as stated above the benchmark runs OK on native Linux guest disk instead of shared folder, so it seems the problem is not in bonnie++ code.
- There's no error / no message appearing at VBox.log for the running VM right before, during or after the benchmark. See attached file VBox-20110421-1939.log.
BTM3505 (self reference, please ignore)