Open BellCubeDev opened 3 weeks ago
Can you retest with 2.2.6rc1 - it worked here.
A test on zfswin-2.2.6rc1
/ zfs-kmod-zfswin-2.2.6rc1
returned the same results
Oh directories! Way to read the ticket lundman. Ok yeah that didn't. a0c09d372adcbb6d1cb318372710bc62eb3ee535
Just looked over this again and found an artifact from an old version of the bug report before I fully understood the scope of the bug (possibly through a one-off fluke?).
For example, a symbolic link from
T:\CoolFolder\
to the non-existentC:\MichaelsoftBinbows\System32
could not be deleted until you created the folderC:\MichaelsoftBinbows\System32
This was not the case. Symlinks could only be deleted from a Linux system, even if the directory existed. For sanity, I've just checked on the latest version with both a filled and an empty directory and both returned a "not empty" error.
What, even rc4?
System information
zfs-kmod-zfswin-2.2.3rc5
zfswin-2.2.6rc1
zfs-kmod-zfswin-2.2.6rc1
Describe the problem you're observing
When a symbolic link to a directory exists, the symlink cannot be deleted from a ZFS pool, citing a "directory not empty" error. This applies to symlinks with targets on multiple file systems (tested NTFS and ZFS), whether the target actually exists, or whether an existing target actually has contents.
For example, a symbolic link fromThis is an artifact from an old version of the bug report before I fully understood the scope of the bug (possibly through a one-off fluke?). This was not the case. Symlinks could only be deleted from a Linux system.T:\CoolFolder\
to the non-existentC:\MichaelsoftBinbows\System32
could not be deleted until you created the folderC:\MichaelsoftBinbows\System32
Describe how to reproduce the problem
mklink /D link_to_create link_target
syntax. The target directory does not need to exist.New-Item -Path link_to_create -ItemType SymbolicLink -Value link_target
syntax. The target directory needs to exist already or else PowerShell will make a file symlinkInclude any warning/errors/backtraces from the system logs
File explorer gives the following:
The following is returned when using Microsoft's Error Lookup Tool for error code
0x80070091
: