btrfs filesystem resize doesn't do anything [closed]

up vote
2
down vote

favorite

I'm trying to increase the size of /home.

First I extended the LV via:

sudo lvextend --size +1024M /dev/vg_svelte/home

Then I did:

$ sudo btrfs filesystem resize max /home
Resize '/home' of 'max'

Minutes later, nothing has happened, I see:

$ btrfs fil show home
Label: 'home' uuid: 93722fa7-7e8f-418a-a7ca-080aca8db94b
 Total devices 1 FS bytes used 179.03GiB
 devid 1 size 201.00GiB used 200.00GiB path /dev/mapper/vg_svelte-home

The total - used == 1GB.

How do I get btrfs to use the 1GB that I just allocated to its LV?

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

closed as off-topic by Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man Oct 22 '17 at 18:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â€“ Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man

If this question can be reworded to fit the rules in the help center, please edit the question.

Anything in the output of dmesg after running the resize command (again)?
â€“Â Hauke Laging
Oct 14 '17 at 15:04

add a commentÂ |Â

up vote
2
down vote

favorite

I'm trying to increase the size of /home.

First I extended the LV via:

sudo lvextend --size +1024M /dev/vg_svelte/home

Then I did:

$ sudo btrfs filesystem resize max /home
Resize '/home' of 'max'

Minutes later, nothing has happened, I see:

$ btrfs fil show home
Label: 'home' uuid: 93722fa7-7e8f-418a-a7ca-080aca8db94b
 Total devices 1 FS bytes used 179.03GiB
 devid 1 size 201.00GiB used 200.00GiB path /dev/mapper/vg_svelte-home

The total - used == 1GB.

How do I get btrfs to use the 1GB that I just allocated to its LV?

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

closed as off-topic by Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man Oct 22 '17 at 18:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â€“ Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man

If this question can be reworded to fit the rules in the help center, please edit the question.

Anything in the output of dmesg after running the resize command (again)?
â€“Â Hauke Laging
Oct 14 '17 at 15:04

add a commentÂ |Â

up vote
2
down vote

favorite

I'm trying to increase the size of /home.

First I extended the LV via:

sudo lvextend --size +1024M /dev/vg_svelte/home

Then I did:

$ sudo btrfs filesystem resize max /home
Resize '/home' of 'max'

Minutes later, nothing has happened, I see:

$ btrfs fil show home
Label: 'home' uuid: 93722fa7-7e8f-418a-a7ca-080aca8db94b
 Total devices 1 FS bytes used 179.03GiB
 devid 1 size 201.00GiB used 200.00GiB path /dev/mapper/vg_svelte-home

The total - used == 1GB.

How do I get btrfs to use the 1GB that I just allocated to its LV?

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

I'm trying to increase the size of /home.

First I extended the LV via:

sudo lvextend --size +1024M /dev/vg_svelte/home

Then I did:

$ sudo btrfs filesystem resize max /home
Resize '/home' of 'max'

Minutes later, nothing has happened, I see:

$ btrfs fil show home
Label: 'home' uuid: 93722fa7-7e8f-418a-a7ca-080aca8db94b
 Total devices 1 FS bytes used 179.03GiB
 devid 1 size 201.00GiB used 200.00GiB path /dev/mapper/vg_svelte-home

The total - used == 1GB.

How do I get btrfs to use the 1GB that I just allocated to its LV?

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

asked Oct 14 '17 at 14:41

Tom Hale

5,89422576

closed as off-topic by Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man Oct 22 '17 at 18:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â€“ Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man

If this question can be reworded to fit the rules in the help center, please edit the question.

closed as off-topic by Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man Oct 22 '17 at 18:57

This question appears to be off-topic. The users who voted to close gave this specific reason:

"Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." â€“ Jeff Schaller, SatÃ…Â Katsura, Stephen Rauch, Romeo Ninov, G-Man

If this question can be reworded to fit the rules in the help center, please edit the question.

Anything in the output of dmesg after running the resize command (again)?
â€“Â Hauke Laging
Oct 14 '17 at 15:04

add a commentÂ |Â

Anything in the output of dmesg after running the resize command (again)?
â€“Â Hauke Laging
Oct 14 '17 at 15:04

Anything in the output of dmesg after running the resize command (again)?
â€“Â Hauke Laging
Oct 14 '17 at 15:04

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
0
down vote

accepted

This really isn't an answer, but I tried again to get the dmesg output requested, and it worked this time.

I searched back in time and had multiple lines like:

BTRFS info (device dm-2): new size for /dev/mapper/vg_svelte-home is 215817912320

But there was never an error message.

Perhaps btrfs needs a status command for showing a resize in progress, or there was a gremlin in the system.

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

add a commentÂ |Â

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
0
down vote

accepted

This really isn't an answer, but I tried again to get the dmesg output requested, and it worked this time.

I searched back in time and had multiple lines like:

BTRFS info (device dm-2): new size for /dev/mapper/vg_svelte-home is 215817912320

But there was never an error message.

Perhaps btrfs needs a status command for showing a resize in progress, or there was a gremlin in the system.

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

add a commentÂ |Â

up vote
0
down vote

accepted

This really isn't an answer, but I tried again to get the dmesg output requested, and it worked this time.

I searched back in time and had multiple lines like:

BTRFS info (device dm-2): new size for /dev/mapper/vg_svelte-home is 215817912320

But there was never an error message.

Perhaps btrfs needs a status command for showing a resize in progress, or there was a gremlin in the system.

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

add a commentÂ |Â

up vote
0
down vote

accepted

This really isn't an answer, but I tried again to get the dmesg output requested, and it worked this time.

I searched back in time and had multiple lines like:

BTRFS info (device dm-2): new size for /dev/mapper/vg_svelte-home is 215817912320

But there was never an error message.

Perhaps btrfs needs a status command for showing a resize in progress, or there was a gremlin in the system.

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

This really isn't an answer, but I tried again to get the dmesg output requested, and it worked this time.

I searched back in time and had multiple lines like:

BTRFS info (device dm-2): new size for /dev/mapper/vg_svelte-home is 215817912320

But there was never an error message.

Perhaps btrfs needs a status command for showing a resize in progress, or there was a gremlin in the system.

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

answered Oct 18 '17 at 9:35

Tom Hale

5,89422576

add a commentÂ |Â

搜尋此網誌

mjhjmtu