Resizing partitions for EC2 FreeBSD instance without reboot
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I modified the volume size for a partition on AWS Console and it does not show up in gpart show. It does show up after the reboot. I didn't have to reboot an Ubuntu instance to resize. Am I missing any steps here or is reboot required for FreeBSD 11.0 instances in this case? Can we do a service restart or something that can avoid reboot?
Before reboot:
=> 3 20971509 ada0 GPT (10G)
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
After reboot:
=> 3 20971509 ada0 GPT (40G) [CORRUPT]
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
partition freebsd amazon-ec2
asked Nov 9 '17 at 21:08
pdns
656
add a comment |Â
up vote
2
down vote
favorite
I modified the volume size for a partition on AWS Console and it does not show up in gpart show. It does show up after the reboot. I didn't have to reboot an Ubuntu instance to resize. Am I missing any steps here or is reboot required for FreeBSD 11.0 instances in this case? Can we do a service restart or something that can avoid reboot?
Before reboot:
=> 3 20971509 ada0 GPT (10G)
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
After reboot:
=> 3 20971509 ada0 GPT (40G) [CORRUPT]
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
partition freebsd amazon-ec2
asked Nov 9 '17 at 21:08
pdns
656
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
I thinkgpart recoverdid not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something likerecovered. I can try reproducing it again
– pdns
Nov 10 '17 at 16:51
add a comment |Â
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I modified the volume size for a partition on AWS Console and it does not show up in gpart show. It does show up after the reboot. I didn't have to reboot an Ubuntu instance to resize. Am I missing any steps here or is reboot required for FreeBSD 11.0 instances in this case? Can we do a service restart or something that can avoid reboot?
Before reboot:
=> 3 20971509 ada0 GPT (10G)
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
After reboot:
=> 3 20971509 ada0 GPT (40G) [CORRUPT]
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
partition freebsd amazon-ec2
asked Nov 9 '17 at 21:08
pdns
656
I modified the volume size for a partition on AWS Console and it does not show up in gpart show. It does show up after the reboot. I didn't have to reboot an Ubuntu instance to resize. Am I missing any steps here or is reboot required for FreeBSD 11.0 instances in this case? Can we do a service restart or something that can avoid reboot?
Before reboot:
=> 3 20971509 ada0 GPT (10G)
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
After reboot:
=> 3 20971509 ada0 GPT (40G) [CORRUPT]
3 125 1 freebsd-boot (63K)
128 20971384 2 freebsd-ufs (10G)
partition freebsd amazon-ec2
asked Nov 9 '17 at 21:08
pdns
656
edited Nov 10 '17 at 16:55
asked Nov 9 '17 at 21:08
pdns
656
asked Nov 9 '17 at 21:08
pdns
656
asked Nov 9 '17 at 21:08
pdns
656
656
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
I thinkgpart recoverdid not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something likerecovered. I can try reproducing it again
– pdns
Nov 10 '17 at 16:51
add a comment |Â
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
I thinkgpart recoverdid not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something likerecovered. I can try reproducing it again
– pdns
Nov 10 '17 at 16:51
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
I think
gpart recover did not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something like recovered. I can try reproducing it again– pdns
Nov 10 '17 at 16:51
I think
gpart recover did not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something like recovered. I can try reproducing it again– pdns
Nov 10 '17 at 16:51
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f403614%2fresizing-partitions-for-ec2-freebsd-instance-without-reboot%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
did you run gpart recover?
– arved
Nov 10 '17 at 15:47
I think
gpart recoverdid not do anything before the reboot. I do not remember the error but I think it was something like 'nothing to recover'. After reboot, the output was something likerecovered. I can try reproducing it again– pdns
Nov 10 '17 at 16:51