You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try to rename a file (or folder) in the immediate directory behind a symlink/junction (same subvolume), the file to be renamed gets deleted. If the junction points into a different subvolume you just get an error that the parent directory (symlink name) does not exist and renaming fails without the file being deleted. The simplest way to test this is via Explorer: Right-Click - New - Folder and enter a folder name, which causes the "New Folder" to be renamed implicitly. In subdirectories below the symlink/junction this problem does not appear.
From terminal (tried CMD and NU shell) mv always works correctly. The strange behavior only happens in Explorer and Double Commander. The symlinks have been created using Double Commander via Menu: Files - Create symlink … (first menu, first menu entry)
The text was updated successfully, but these errors were encountered:
winbtrfs 1.9
Windows 10.0.19045.4651
If you try to rename a file (or folder) in the immediate directory behind a symlink/junction (same subvolume), the file to be renamed gets deleted. If the junction points into a different subvolume you just get an error that the parent directory (symlink name) does not exist and renaming fails without the file being deleted. The simplest way to test this is via Explorer: Right-Click - New - Folder and enter a folder name, which causes the "New Folder" to be renamed implicitly. In subdirectories below the symlink/junction this problem does not appear.
From terminal (tried CMD and NU shell)
mv
always works correctly. The strange behavior only happens in Explorer and Double Commander. The symlinks have been created using Double Commander via Menu: Files - Create symlink … (first menu, first menu entry)The text was updated successfully, but these errors were encountered: