Custom Query (44 matches)
Results (22 - 24 of 44)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #31 | fixed | Testticket to check notification | ||
| Description |
please ignore, only for test |
|||
| #34 | fixed | Canceled deletion deletes anyway but reports no file(s) deleted | ||
| Description |
Pressing Ctrl-C during a del operation results in the current deletion completing, yet not being counted as a deleted file in the resulting report. In addition, the bytes freed count is incorrect (too low). Example: [j:\]del some-huge-file.dat
Deleting J:\some-huge-file.dat
^C
0 files deleted 18,587,648 bytes freed
[j:\]del some-huge-file.dat /f
There are no more files. "J:\some-huge-file.dat"
0 files deleted
[j:\]undelete /f some-huge-file.dat
Discarding J:\some-huge-file.dat.
J:\SOME-HUGE-FILE.DAT
Do you want to discard this file (Y/N)?
y
The file in question was 756,717,655 bytes in length. Allowing for space on disk, surely more than 18,587,648 bytes had to have been freed. |
|||
| #38 | invalid | MOVE to a different volume should not trigger write to DELDIR | ||
| Description |
When MOVE is used to relocate a file from one volume to another, the file being moved is copied to DELDIR for the source volume. This is inconsistent with the intention of a move, which is not to delete, but rather to relocate. Use case is when a user needs to free up space on a given volume, so he moves files to a different volume. This exercise is futile, particularly if DELDIR is large, as the moved files are also copied to DELDIR in the operation. |
|||
