Checking destination directory after “No space left on device” error
Clash Royale CLAN TAG#URR8PPP
My latest backup attempt with rdiff-backup failed due to "[Errno 28] No space left on device". And it's true, according to du there are 0 bytes available on the backup device.
When I now try to revert the directory to the state before the unsuccessful session by simply starting another backup attempt, I also get [Errno 28]. The next idea I had was to get rid of some old backup increments to gain some fresh disk space.
To see the list of backup increments, I invoked rdiff-backup -l mirror_dir which results in
Fatal Error: Previous backup to mirror_dir seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to state before unsuccessful session.
Then I did what the message told me and ran rdiff-backup --check-destination-dir mirror_dir which again gives me the now already famous [Errno 28]. It seems like I am in a dead end, where I cannot do anything anymore, not even free some disk space which action seems to be the only solution to this problem.
Is there a way out of this situation?
rdiff-backup
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
add a comment |
My latest backup attempt with rdiff-backup failed due to "[Errno 28] No space left on device". And it's true, according to du there are 0 bytes available on the backup device.
When I now try to revert the directory to the state before the unsuccessful session by simply starting another backup attempt, I also get [Errno 28]. The next idea I had was to get rid of some old backup increments to gain some fresh disk space.
To see the list of backup increments, I invoked rdiff-backup -l mirror_dir which results in
Fatal Error: Previous backup to mirror_dir seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to state before unsuccessful session.
Then I did what the message told me and ran rdiff-backup --check-destination-dir mirror_dir which again gives me the now already famous [Errno 28]. It seems like I am in a dead end, where I cannot do anything anymore, not even free some disk space which action seems to be the only solution to this problem.
Is there a way out of this situation?
rdiff-backup
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26
add a comment |
My latest backup attempt with rdiff-backup failed due to "[Errno 28] No space left on device". And it's true, according to du there are 0 bytes available on the backup device.
When I now try to revert the directory to the state before the unsuccessful session by simply starting another backup attempt, I also get [Errno 28]. The next idea I had was to get rid of some old backup increments to gain some fresh disk space.
To see the list of backup increments, I invoked rdiff-backup -l mirror_dir which results in
Fatal Error: Previous backup to mirror_dir seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to state before unsuccessful session.
Then I did what the message told me and ran rdiff-backup --check-destination-dir mirror_dir which again gives me the now already famous [Errno 28]. It seems like I am in a dead end, where I cannot do anything anymore, not even free some disk space which action seems to be the only solution to this problem.
Is there a way out of this situation?
rdiff-backup
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
My latest backup attempt with rdiff-backup failed due to "[Errno 28] No space left on device". And it's true, according to du there are 0 bytes available on the backup device.
When I now try to revert the directory to the state before the unsuccessful session by simply starting another backup attempt, I also get [Errno 28]. The next idea I had was to get rid of some old backup increments to gain some fresh disk space.
To see the list of backup increments, I invoked rdiff-backup -l mirror_dir which results in
Fatal Error: Previous backup to mirror_dir seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to state before unsuccessful session.
Then I did what the message told me and ran rdiff-backup --check-destination-dir mirror_dir which again gives me the now already famous [Errno 28]. It seems like I am in a dead end, where I cannot do anything anymore, not even free some disk space which action seems to be the only solution to this problem.
Is there a way out of this situation?
rdiff-backup
rdiff-backup
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
asked Jun 4 '15 at 21:17
zepp.leezepp.lee
235210
235210
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26
add a comment |
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26
add a comment |
1 Answer
1
active
oldest
votes
Other than growing the underlying filesystem, there isn't a good way, but that should be pretty easy — you have many options there, including getting a new, larger drive and mirroring the data over (using something like cp -a or rsync -a). The annoyance with large backup volumes is that this can take a very long time.
If you are like me and have multiple backups on the same filesystem, you can easily find space by moving a backup or large file somewhere else temporarily.
To avoid this problem, I have learned to leave a .00DOORSTOP file in my backup directory that I can rm when I need the space. I currently have the file at 1GB, which should be enough to allow me to create more space if needed — rdiff-backup needs a minimal amount of space to run (probably to create temporary files). It can't be a sparse file, obviously; I create it by using dd:
dd if=/dev/zero of=.00DOORSTOOP bs=1G count=1
answered Jul 24 '17 at 13:05
kikokiko
1054
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f207640%2fchecking-destination-directory-after-no-space-left-on-device-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Other than growing the underlying filesystem, there isn't a good way, but that should be pretty easy — you have many options there, including getting a new, larger drive and mirroring the data over (using something like cp -a or rsync -a). The annoyance with large backup volumes is that this can take a very long time.
If you are like me and have multiple backups on the same filesystem, you can easily find space by moving a backup or large file somewhere else temporarily.
To avoid this problem, I have learned to leave a .00DOORSTOP file in my backup directory that I can rm when I need the space. I currently have the file at 1GB, which should be enough to allow me to create more space if needed — rdiff-backup needs a minimal amount of space to run (probably to create temporary files). It can't be a sparse file, obviously; I create it by using dd:
dd if=/dev/zero of=.00DOORSTOOP bs=1G count=1
answered Jul 24 '17 at 13:05
kikokiko
1054
add a comment |
Other than growing the underlying filesystem, there isn't a good way, but that should be pretty easy — you have many options there, including getting a new, larger drive and mirroring the data over (using something like cp -a or rsync -a). The annoyance with large backup volumes is that this can take a very long time.
If you are like me and have multiple backups on the same filesystem, you can easily find space by moving a backup or large file somewhere else temporarily.
To avoid this problem, I have learned to leave a .00DOORSTOP file in my backup directory that I can rm when I need the space. I currently have the file at 1GB, which should be enough to allow me to create more space if needed — rdiff-backup needs a minimal amount of space to run (probably to create temporary files). It can't be a sparse file, obviously; I create it by using dd:
dd if=/dev/zero of=.00DOORSTOOP bs=1G count=1
answered Jul 24 '17 at 13:05
kikokiko
1054
add a comment |
Other than growing the underlying filesystem, there isn't a good way, but that should be pretty easy — you have many options there, including getting a new, larger drive and mirroring the data over (using something like cp -a or rsync -a). The annoyance with large backup volumes is that this can take a very long time.
If you are like me and have multiple backups on the same filesystem, you can easily find space by moving a backup or large file somewhere else temporarily.
To avoid this problem, I have learned to leave a .00DOORSTOP file in my backup directory that I can rm when I need the space. I currently have the file at 1GB, which should be enough to allow me to create more space if needed — rdiff-backup needs a minimal amount of space to run (probably to create temporary files). It can't be a sparse file, obviously; I create it by using dd:
dd if=/dev/zero of=.00DOORSTOOP bs=1G count=1
answered Jul 24 '17 at 13:05
kikokiko
1054
Other than growing the underlying filesystem, there isn't a good way, but that should be pretty easy — you have many options there, including getting a new, larger drive and mirroring the data over (using something like cp -a or rsync -a). The annoyance with large backup volumes is that this can take a very long time.
If you are like me and have multiple backups on the same filesystem, you can easily find space by moving a backup or large file somewhere else temporarily.
To avoid this problem, I have learned to leave a .00DOORSTOP file in my backup directory that I can rm when I need the space. I currently have the file at 1GB, which should be enough to allow me to create more space if needed — rdiff-backup needs a minimal amount of space to run (probably to create temporary files). It can't be a sparse file, obviously; I create it by using dd:
dd if=/dev/zero of=.00DOORSTOOP bs=1G count=1
answered Jul 24 '17 at 13:05
kikokiko
1054
edited Feb 18 at 17:59
answered Jul 24 '17 at 13:05
kikokiko
1054
answered Jul 24 '17 at 13:05
kikokiko
1054
answered Jul 24 '17 at 13:05
kikokiko
1054
1054
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f207640%2fchecking-destination-directory-after-no-space-left-on-device-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You cannot manually delete stuff?
– PythonNut
Jun 4 '15 at 21:30
You mean that I should remove the old increments manually? How would one do that?
– zepp.lee
Jun 5 '15 at 9:28
Does this volume contain only backups ? Are there no other files there that could go ? Also, rdiff-backup sometimes needs a lot of space in /tmp and throws this error when there is not enough space there. You can alleviate that problem by creating a folder on some very big volume and issuing: export TMPDIR=/path/to/massive/volume/tmp
– thecarpy
Jun 5 '15 at 11:31
Yes, the volume contains backups exclusively. And I don't think the temporary directory has anything to do with it (yet I still tried to change it and it failed).
– zepp.lee
Jun 5 '15 at 19:26