Attempting to increase the size of a Linux LVM Disk
-
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
Is this improper syntax?
Try +3.91.
Also, why not have the data on its own volume? It's more flexible that way.
-
If the +doesn't work you will have to add it to the existing size. So if its 5TB it would be 8.91
-
Just appears that the size is too small.
-
@scottalanmiller That confuses me because each is 1.9T
-
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller That confuses me because each is 1.9T
Why? Your total from your LVS command looks like 3.89TB but you are trying to expand to 3.91TB.
-
@scottalanmiller LVS is 3.89T
-
I edited while you were typing. I read the wrong field. But it is still too small. The FS must be smaller than the container holding it.
-
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
I edited while you were typing. I read the wrong field. But it is still too small. The FS must be smaller than the container holding it.
How much smaller? even 3.86 kicks back the same error
-
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
I edited while you were typing. I read the wrong field. But it is still too small. The FS must be smaller than the container holding it.
How much smaller? even 3.86 kicks back the same error
Try something like 3.4TB. Remember FS overhead.
-
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
I edited while you were typing. I read the wrong field. But it is still too small. The FS must be smaller than the container holding it.
How much smaller? even 3.86 kicks back the same error
Try something like 3.4TB. Remember FS overhead.
-
Does the + reflect the entire size or just the amount of growth?
-
-D goes to total. Do the command instead with the -d option and no number...
xfs_growfs /dev/mapper/centos-root -d -
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
-D goes to total. Do the command instead with the -d option and no number...
xfs_growfs /dev/mapper/centos-root -dI can't believe a capital D caused all of this
/wrists
Thanks Scott
-
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
-D goes to total. Do the command instead with the -d option and no number...
xfs_growfs /dev/mapper/centos-root -dI can't believe a capital D caused all of this
/wrists
Thanks Scott
Well, the capital D made us have to know the size. The lower case d calculated it for us. The upper case one would have been fine had the number we gave been the right one. But that's just a pain.
-
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
-D goes to total. Do the command instead with the -d option and no number...
xfs_growfs /dev/mapper/centos-root -dI can't believe a capital D caused all of this
/wrists
Thanks Scott
Well, the capital D made us have to know the size. The lower case d calculated it for us. The upper case one would have been fine had the number we gave been the right one. But that's just a pain.
I'm unsure why it was considered wrong. I tried a much much smaller size and it didnt work either
-
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
@wirestyle22 said in Attempting to increase the size of a Linux LVM Disk:
@scottalanmiller said in Attempting to increase the size of a Linux LVM Disk:
-D goes to total. Do the command instead with the -d option and no number...
xfs_growfs /dev/mapper/centos-root -dI can't believe a capital D caused all of this
/wrists
Thanks Scott
Well, the capital D made us have to know the size. The lower case d calculated it for us. The upper case one would have been fine had the number we gave been the right one. But that's just a pain.
I'm unsure why it was considered wrong. I tried a much much smaller size and it didnt work either
How small did you try it?
-
How big did it make in the end?
-
3.9TB
-
Oh I thought you were specifying a size on purpose. You can just use the -r flag with lvextend to automatically grow the file system.
-
Nah, I'm doing this just as a learning experience. I used my Plex server as a test dummy. Thanks for the help everybody
