Accidentally trashed large file
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
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.
shell-script debian file-copy ntfs deleted-files
add a comment |Â
up vote
2
down vote
favorite
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.
shell-script debian file-copy ntfs deleted-files
1
What does "not work" with your attempt withrsync
?
â 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
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
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.
shell-script debian file-copy ntfs deleted-files
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.
shell-script debian file-copy ntfs deleted-files
asked Nov 27 '17 at 9:56
m c squared
32827
32827
1
What does "not work" with your attempt withrsync
?
â 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
add a comment |Â
1
What does "not work" with your attempt withrsync
?
â 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
add a comment |Â
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.
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
add a comment |Â
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.
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
add a comment |Â
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.
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
add a comment |Â
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.
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.
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
add a comment |Â
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
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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