Accidentally trashed large file

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite
1












I accidentally moved an entire directory of ~100GB to trash. I was trying to place it in bookmarks but dragged it into trash. It's there in the trash. But




when i try to restore I run out of space on the disk




Prior to deletion I had less than 50GB free on disk, if I need to restore the normal way I need about 68GB more free on the disk. That is




if I have to restore I have to delete every file from trash
immediately after restoring it




so i can revert back to initial state. I tried to use "rsync -av --remove-source-files /Trash/file /Dest"
but it also doesn't work.
Any suggestions to solve the problem ?
I use MX17 beta 2 based on debian stable.The disk is NTFS formatted.







share|improve this question
















  • 1




    What does "not work" with your attempt with rsync?
    – Kusalananda
    Nov 27 '17 at 10:53










  • @Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
    – m c squared
    Nov 27 '17 at 12:53










  • Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
    – Kusalananda
    Nov 27 '17 at 12:55














up vote
2
down vote

favorite
1












I accidentally moved an entire directory of ~100GB to trash. I was trying to place it in bookmarks but dragged it into trash. It's there in the trash. But




when i try to restore I run out of space on the disk




Prior to deletion I had less than 50GB free on disk, if I need to restore the normal way I need about 68GB more free on the disk. That is




if I have to restore I have to delete every file from trash
immediately after restoring it




so i can revert back to initial state. I tried to use "rsync -av --remove-source-files /Trash/file /Dest"
but it also doesn't work.
Any suggestions to solve the problem ?
I use MX17 beta 2 based on debian stable.The disk is NTFS formatted.







share|improve this question
















  • 1




    What does "not work" with your attempt with rsync?
    – Kusalananda
    Nov 27 '17 at 10:53










  • @Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
    – m c squared
    Nov 27 '17 at 12:53










  • Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
    – Kusalananda
    Nov 27 '17 at 12:55












up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





I accidentally moved an entire directory of ~100GB to trash. I was trying to place it in bookmarks but dragged it into trash. It's there in the trash. But




when i try to restore I run out of space on the disk




Prior to deletion I had less than 50GB free on disk, if I need to restore the normal way I need about 68GB more free on the disk. That is




if I have to restore I have to delete every file from trash
immediately after restoring it




so i can revert back to initial state. I tried to use "rsync -av --remove-source-files /Trash/file /Dest"
but it also doesn't work.
Any suggestions to solve the problem ?
I use MX17 beta 2 based on debian stable.The disk is NTFS formatted.







share|improve this question












I accidentally moved an entire directory of ~100GB to trash. I was trying to place it in bookmarks but dragged it into trash. It's there in the trash. But




when i try to restore I run out of space on the disk




Prior to deletion I had less than 50GB free on disk, if I need to restore the normal way I need about 68GB more free on the disk. That is




if I have to restore I have to delete every file from trash
immediately after restoring it




so i can revert back to initial state. I tried to use "rsync -av --remove-source-files /Trash/file /Dest"
but it also doesn't work.
Any suggestions to solve the problem ?
I use MX17 beta 2 based on debian stable.The disk is NTFS formatted.









share|improve this question











share|improve this question




share|improve this question










asked Nov 27 '17 at 9:56









m c squared

32827




32827







  • 1




    What does "not work" with your attempt with rsync?
    – Kusalananda
    Nov 27 '17 at 10:53










  • @Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
    – m c squared
    Nov 27 '17 at 12:53










  • Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
    – Kusalananda
    Nov 27 '17 at 12:55












  • 1




    What does "not work" with your attempt with rsync?
    – Kusalananda
    Nov 27 '17 at 10:53










  • @Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
    – m c squared
    Nov 27 '17 at 12:53










  • Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
    – Kusalananda
    Nov 27 '17 at 12:55







1




1




What does "not work" with your attempt with rsync?
– Kusalananda
Nov 27 '17 at 10:53




What does "not work" with your attempt with rsync?
– Kusalananda
Nov 27 '17 at 10:53












@Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
– m c squared
Nov 27 '17 at 12:53




@Kusalananda The same error "No space left on device", On trying with file manager "Error splicing: No more space"
– m c squared
Nov 27 '17 at 12:53












Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
– Kusalananda
Nov 27 '17 at 12:55




Could you move the files one by one, either manually or, if there are too many of them, with a simple loop?
– Kusalananda
Nov 27 '17 at 12:55










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










if you are moving to the same partition then



mv /source/* /dest/


should work without creating a copy or consuming more space



Alternatively, just do the same exercise with /dest/ on an external drive or partition then copy them back once you have cleared space in your original location.






share|improve this answer




















  • Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
    – m c squared
    Nov 28 '17 at 9:35











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407245%2faccidentally-trashed-large-file%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
2
down vote



accepted










if you are moving to the same partition then



mv /source/* /dest/


should work without creating a copy or consuming more space



Alternatively, just do the same exercise with /dest/ on an external drive or partition then copy them back once you have cleared space in your original location.






share|improve this answer




















  • Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
    – m c squared
    Nov 28 '17 at 9:35















up vote
2
down vote



accepted










if you are moving to the same partition then



mv /source/* /dest/


should work without creating a copy or consuming more space



Alternatively, just do the same exercise with /dest/ on an external drive or partition then copy them back once you have cleared space in your original location.






share|improve this answer




















  • Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
    – m c squared
    Nov 28 '17 at 9:35













up vote
2
down vote



accepted







up vote
2
down vote



accepted






if you are moving to the same partition then



mv /source/* /dest/


should work without creating a copy or consuming more space



Alternatively, just do the same exercise with /dest/ on an external drive or partition then copy them back once you have cleared space in your original location.






share|improve this answer












if you are moving to the same partition then



mv /source/* /dest/


should work without creating a copy or consuming more space



Alternatively, just do the same exercise with /dest/ on an external drive or partition then copy them back once you have cleared space in your original location.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 27 '17 at 15:46









bu5hman

1,164214




1,164214











  • Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
    – m c squared
    Nov 28 '17 at 9:35

















  • Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
    – m c squared
    Nov 28 '17 at 9:35
















Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
– m c squared
Nov 28 '17 at 9:35





Unfortunately this is my only large partition and i dont have external disks... I'll try to use mv again thank you for pointing me to internal working of mv and i'll let you know the progress.
– m c squared
Nov 28 '17 at 9:35


















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f407245%2faccidentally-trashed-large-file%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Christian Cage

How to properly install USB display driver for Fresco Logic FL2000DX on Ubuntu?