Can I reboot during a btrfs replace and then resume it?
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I have a damaged hard disk with a lot of read errors. I'm currently doing a btrfs replace, but after 24 hours at just over 5% done, this is a problem: it's my work computer; I'm currently booted onto a Live USB, but I need to go back to the existing Ubuntu to continue my work (it has a really hard time booting in with all the read errors, but is able to make it sometimes).
Note: the entire hard disk, or at least this partition of it, curently reads at ~500 KBps, even when there aren't read errors - the btrfs replace status currently reports 0 read errors.
So I have two options:
1) just shut down, reboot into the other OS, and try to run the same btrfs replace start command I first ran.
2) cancel the current replace operation, which may take forever (I already tried a cancel before, a minute into the replace, and it seemed to take just as long to cancel) and would undo a day's hard-earned transfer progress.
3) admit defeat and just settle into this LiveUSB OS for the next 2-3 weeks and pray that the cleaning people don't bump the USB stick.
btrfs replace
asked Aug 27 '16 at 7:38
sssheridan
1264
add a comment |
up vote
3
down vote
favorite
I have a damaged hard disk with a lot of read errors. I'm currently doing a btrfs replace, but after 24 hours at just over 5% done, this is a problem: it's my work computer; I'm currently booted onto a Live USB, but I need to go back to the existing Ubuntu to continue my work (it has a really hard time booting in with all the read errors, but is able to make it sometimes).
Note: the entire hard disk, or at least this partition of it, curently reads at ~500 KBps, even when there aren't read errors - the btrfs replace status currently reports 0 read errors.
So I have two options:
1) just shut down, reboot into the other OS, and try to run the same btrfs replace start command I first ran.
2) cancel the current replace operation, which may take forever (I already tried a cancel before, a minute into the replace, and it seemed to take just as long to cancel) and would undo a day's hard-earned transfer progress.
3) admit defeat and just settle into this LiveUSB OS for the next 2-3 weeks and pray that the cleaning people don't bump the USB stick.
btrfs replace
asked Aug 27 '16 at 7:38
sssheridan
1264
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a damaged hard disk with a lot of read errors. I'm currently doing a btrfs replace, but after 24 hours at just over 5% done, this is a problem: it's my work computer; I'm currently booted onto a Live USB, but I need to go back to the existing Ubuntu to continue my work (it has a really hard time booting in with all the read errors, but is able to make it sometimes).
Note: the entire hard disk, or at least this partition of it, curently reads at ~500 KBps, even when there aren't read errors - the btrfs replace status currently reports 0 read errors.
So I have two options:
1) just shut down, reboot into the other OS, and try to run the same btrfs replace start command I first ran.
2) cancel the current replace operation, which may take forever (I already tried a cancel before, a minute into the replace, and it seemed to take just as long to cancel) and would undo a day's hard-earned transfer progress.
3) admit defeat and just settle into this LiveUSB OS for the next 2-3 weeks and pray that the cleaning people don't bump the USB stick.
btrfs replace
asked Aug 27 '16 at 7:38
sssheridan
1264
I have a damaged hard disk with a lot of read errors. I'm currently doing a btrfs replace, but after 24 hours at just over 5% done, this is a problem: it's my work computer; I'm currently booted onto a Live USB, but I need to go back to the existing Ubuntu to continue my work (it has a really hard time booting in with all the read errors, but is able to make it sometimes).
Note: the entire hard disk, or at least this partition of it, curently reads at ~500 KBps, even when there aren't read errors - the btrfs replace status currently reports 0 read errors.
So I have two options:
1) just shut down, reboot into the other OS, and try to run the same btrfs replace start command I first ran.
2) cancel the current replace operation, which may take forever (I already tried a cancel before, a minute into the replace, and it seemed to take just as long to cancel) and would undo a day's hard-earned transfer progress.
3) admit defeat and just settle into this LiveUSB OS for the next 2-3 weeks and pray that the cleaning people don't bump the USB stick.
btrfs replace
btrfs replace
asked Aug 27 '16 at 7:38
sssheridan
1264
asked Aug 27 '16 at 7:38
sssheridan
1264
edited Aug 27 '16 at 7:45
asked Aug 27 '16 at 7:38
sssheridan
1264
asked Aug 27 '16 at 7:38
sssheridan
1264
asked Aug 27 '16 at 7:38
sssheridan
1264
1264
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
Answering my question: I tried it, and everything is on fire. Input/output errors everywhere and somehow my filesystem thinks it's RAID1 when it's not. To be fair, a partition was already corrupt and that seems to be part of the problem, but nevertheless I Do Not Recommend doing this. Do a btrfs replace cancel and wait it out.
answered Aug 29 '16 at 9:42
sssheridan
1264
add a comment |
up vote
1
down vote
Reviving this question because it's the top Google result when searching for "btrfs replace resume" and the existing answer doesn't tell the whole story.
The replace process automatically resumes after a reboot (much like a balance). I've even had to do a hard-reset during a replace operation and the process happily continued after rebooting and remounting the filesystem. So my guess is that it wasn't the interrupted replace operation itself that gave sssheridan all these problems, but rather the circumstances of having to boot from a dying harddisk.
When mounting after an interrupted replace, a log-line like this is printed:
BTRFS info (device sdh1): continuing dev_replace from /dev/sdb1 (devid 5) to target /dev/sdh1 @95%
The last number is the completion percentage.
answered Nov 22 at 21:08
Bart Noordervliet
112
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Answering my question: I tried it, and everything is on fire. Input/output errors everywhere and somehow my filesystem thinks it's RAID1 when it's not. To be fair, a partition was already corrupt and that seems to be part of the problem, but nevertheless I Do Not Recommend doing this. Do a btrfs replace cancel and wait it out.
answered Aug 29 '16 at 9:42
sssheridan
1264
add a comment |
up vote
1
down vote
Answering my question: I tried it, and everything is on fire. Input/output errors everywhere and somehow my filesystem thinks it's RAID1 when it's not. To be fair, a partition was already corrupt and that seems to be part of the problem, but nevertheless I Do Not Recommend doing this. Do a btrfs replace cancel and wait it out.
answered Aug 29 '16 at 9:42
sssheridan
1264
add a comment |
up vote
1
down vote
up vote
1
down vote
Answering my question: I tried it, and everything is on fire. Input/output errors everywhere and somehow my filesystem thinks it's RAID1 when it's not. To be fair, a partition was already corrupt and that seems to be part of the problem, but nevertheless I Do Not Recommend doing this. Do a btrfs replace cancel and wait it out.
answered Aug 29 '16 at 9:42
sssheridan
1264
Answering my question: I tried it, and everything is on fire. Input/output errors everywhere and somehow my filesystem thinks it's RAID1 when it's not. To be fair, a partition was already corrupt and that seems to be part of the problem, but nevertheless I Do Not Recommend doing this. Do a btrfs replace cancel and wait it out.
answered Aug 29 '16 at 9:42
sssheridan
1264
answered Aug 29 '16 at 9:42
sssheridan
1264
answered Aug 29 '16 at 9:42
sssheridan
1264
answered Aug 29 '16 at 9:42
sssheridan
1264
1264
add a comment |
add a comment |
up vote
1
down vote
Reviving this question because it's the top Google result when searching for "btrfs replace resume" and the existing answer doesn't tell the whole story.
The replace process automatically resumes after a reboot (much like a balance). I've even had to do a hard-reset during a replace operation and the process happily continued after rebooting and remounting the filesystem. So my guess is that it wasn't the interrupted replace operation itself that gave sssheridan all these problems, but rather the circumstances of having to boot from a dying harddisk.
When mounting after an interrupted replace, a log-line like this is printed:
BTRFS info (device sdh1): continuing dev_replace from /dev/sdb1 (devid 5) to target /dev/sdh1 @95%
The last number is the completion percentage.
answered Nov 22 at 21:08
Bart Noordervliet
112
add a comment |
up vote
1
down vote
Reviving this question because it's the top Google result when searching for "btrfs replace resume" and the existing answer doesn't tell the whole story.
The replace process automatically resumes after a reboot (much like a balance). I've even had to do a hard-reset during a replace operation and the process happily continued after rebooting and remounting the filesystem. So my guess is that it wasn't the interrupted replace operation itself that gave sssheridan all these problems, but rather the circumstances of having to boot from a dying harddisk.
When mounting after an interrupted replace, a log-line like this is printed:
BTRFS info (device sdh1): continuing dev_replace from /dev/sdb1 (devid 5) to target /dev/sdh1 @95%
The last number is the completion percentage.
answered Nov 22 at 21:08
Bart Noordervliet
112
add a comment |
up vote
1
down vote
up vote
1
down vote
Reviving this question because it's the top Google result when searching for "btrfs replace resume" and the existing answer doesn't tell the whole story.
The replace process automatically resumes after a reboot (much like a balance). I've even had to do a hard-reset during a replace operation and the process happily continued after rebooting and remounting the filesystem. So my guess is that it wasn't the interrupted replace operation itself that gave sssheridan all these problems, but rather the circumstances of having to boot from a dying harddisk.
When mounting after an interrupted replace, a log-line like this is printed:
BTRFS info (device sdh1): continuing dev_replace from /dev/sdb1 (devid 5) to target /dev/sdh1 @95%
The last number is the completion percentage.
answered Nov 22 at 21:08
Bart Noordervliet
112
Reviving this question because it's the top Google result when searching for "btrfs replace resume" and the existing answer doesn't tell the whole story.
The replace process automatically resumes after a reboot (much like a balance). I've even had to do a hard-reset during a replace operation and the process happily continued after rebooting and remounting the filesystem. So my guess is that it wasn't the interrupted replace operation itself that gave sssheridan all these problems, but rather the circumstances of having to boot from a dying harddisk.
When mounting after an interrupted replace, a log-line like this is printed:
BTRFS info (device sdh1): continuing dev_replace from /dev/sdb1 (devid 5) to target /dev/sdh1 @95%
The last number is the completion percentage.
answered Nov 22 at 21:08
Bart Noordervliet
112
edited Nov 23 at 13:53
answered Nov 22 at 21:08
Bart Noordervliet
112
answered Nov 22 at 21:08
Bart Noordervliet
112
answered Nov 22 at 21:08
Bart Noordervliet
112
112
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f306048%2fcan-i-reboot-during-a-btrfs-replace-and-then-resume-it%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