Skip to content

Fix #733: use PowerShell Move-Item for cross-volume directory on Windows#734

Open
khurram-saeed-malik wants to merge 1 commit intoDataIntellectTech:masterfrom
khurram-saeed-malik:fix/windows-cross-drive-ren
Open

Fix #733: use PowerShell Move-Item for cross-volume directory on Windows#734
khurram-saeed-malik wants to merge 1 commit intoDataIntellectTech:masterfrom
khurram-saeed-malik:fix/windows-cross-drive-ren

Conversation

@khurram-saeed-malik
Copy link
Copy Markdown

@khurram-saeed-malik khurram-saeed-malik commented Apr 16, 2026

Fixes #733

Problem

On Windows, .os.ren used a move command that fails when the source
and destination are on different drives/volumes. This breaks WDB default
writedown mode when the WDB path and HDB path reside on different disks.

Solution

Replace the old Windows move-based implementation with PowerShell's
Move-Item cmdlet, which natively handles:

  • File renames/moves
  • Directory renames/moves
  • Cross-volume moves (different Windows drives/disks)
    The Unix path (mv) is unchanged.

Files Changed

  • code/common/os.q - updated .os.ren

Contributor

Arseni Maiorov
https://github.com/mayoroff

…directory moves on Windows

Replace the robocopy-based .os.ren implementation with a simpler and more
robust approach using PowerShell's Move-Item cmdlet.

Move-Item natively handles:
- File renames/moves
- Directory renames/moves
- Cross-volume moves (different Windows drives/disks)

This fixes the WDB default writedown mode workflow when the WDB path and
HDB path reside on different Windows drives/volumes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

os.ren fails intradisk move on Windows

1 participant