PostgreSQL - Could not extend file No space left on device. HINT: Check free disk space ...

How could we fake a moon landing now?

Can an alien society believe that their star system is the universe?

How to Make a Beautiful Stacked 3D Plot

2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?

Do jazz musicians improvise on the parent scale in addition to the chord-scales?

Delete nth line from bottom

What does "lightly crushed" mean for cardamon pods?

What causes the direction of lightning flashes?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

How to answer "Have you ever been terminated?"

Where are Serre’s lectures at Collège de France to be found?

If my PI received research grants from a company to be able to pay my postdoc salary, did I have a potential conflict interest too?

Using audio cues to encourage good posture

Maximum summed powersets with non-adjacent items

Using et al. for a last / senior author rather than for a first author

When was Kai Tak permanently closed to cargo service?

Fantasy story; one type of magic grows in power with use, but the more powerful they are, they more they are drawn to travel to their source

How do I find out the mythology and history of my Fortress?

Can a party unilaterally change candidates in preparation for a General election?

What is the longest distance a player character can jump in one leap?

Fundamental Solution of the Pell Equation

How would a mousetrap for use in space work?

Would "destroying" Wurmcoil Engine prevent its tokens from being created?

How to convince students of the implication truth values?



PostgreSQL - Could not extend file No space left on device. HINT: Check free disk space



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Come Celebrate our 10 Year Anniversary!fsck on LVM snapshots/tmp used 100% where is files?CentOS partitioningUnexpected behaviour from dfLinux LVM: move free space from a volume group to anotherRoot volume /dev/mapper/centos-root fullResize Centos 7 Root partition set up as xfs file system.Virtualbox disk in CentOS mount/format issuePostgreSQL - Clear space on Linux machineAWS E2 Instance : How to Resize Disk





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I've been inserting data into PostgreSQL DB, and got the error message:



psycopg2.OperationalError: could not extend file "base/16384/61892": No space left on device
HINT: Check free disk space


I am using CentOS 7, and I've checked some of my status on my linux machine:



df -h



enter image description here



I'm pretty new to Linux, and based on the result of my df -h command, I could see that Linux storage system works differently than Windows.



It looks like PostgreSQL is pushing to /dev/mapper/centos-root, but it has only 50 GB available.



Question 1: How can I change it? How can I assign the extra free space that's available in /dev/mapper/centos-home to my ~/centos-root directory?



Question 2: My machine has two Hard disk, 200 GB each. But according to my df-h command, it looked like I only have 200GB available. Why is this the case? How can I take advantage of full 400GB space?



It looks like the problem is that my /dev/mapper/centos-root is all filled up. I have inserted nearly 10,000,000 rows of data with 12 columns in PostgreSQL.



Question 3: Is this big enough to take up 50GB of space?



Thanks!



Edit: output of pvs, vgs, lvs



enter image description here










share|improve this question

























  • Please post the output of pvs; vgs; lvs

    – shodanshok
    Oct 1 '18 at 5:44











  • @shodanshok please check the update. Also, what are the significance of each commands?

    – Eric Kim
    Oct 1 '18 at 6:05






  • 1





    @EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

    – HBruijn
    Oct 1 '18 at 7:15


















0















I've been inserting data into PostgreSQL DB, and got the error message:



psycopg2.OperationalError: could not extend file "base/16384/61892": No space left on device
HINT: Check free disk space


I am using CentOS 7, and I've checked some of my status on my linux machine:



df -h



enter image description here



I'm pretty new to Linux, and based on the result of my df -h command, I could see that Linux storage system works differently than Windows.



It looks like PostgreSQL is pushing to /dev/mapper/centos-root, but it has only 50 GB available.



Question 1: How can I change it? How can I assign the extra free space that's available in /dev/mapper/centos-home to my ~/centos-root directory?



Question 2: My machine has two Hard disk, 200 GB each. But according to my df-h command, it looked like I only have 200GB available. Why is this the case? How can I take advantage of full 400GB space?



It looks like the problem is that my /dev/mapper/centos-root is all filled up. I have inserted nearly 10,000,000 rows of data with 12 columns in PostgreSQL.



Question 3: Is this big enough to take up 50GB of space?



Thanks!



Edit: output of pvs, vgs, lvs



enter image description here










share|improve this question

























  • Please post the output of pvs; vgs; lvs

    – shodanshok
    Oct 1 '18 at 5:44











  • @shodanshok please check the update. Also, what are the significance of each commands?

    – Eric Kim
    Oct 1 '18 at 6:05






  • 1





    @EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

    – HBruijn
    Oct 1 '18 at 7:15














0












0








0








I've been inserting data into PostgreSQL DB, and got the error message:



psycopg2.OperationalError: could not extend file "base/16384/61892": No space left on device
HINT: Check free disk space


I am using CentOS 7, and I've checked some of my status on my linux machine:



df -h



enter image description here



I'm pretty new to Linux, and based on the result of my df -h command, I could see that Linux storage system works differently than Windows.



It looks like PostgreSQL is pushing to /dev/mapper/centos-root, but it has only 50 GB available.



Question 1: How can I change it? How can I assign the extra free space that's available in /dev/mapper/centos-home to my ~/centos-root directory?



Question 2: My machine has two Hard disk, 200 GB each. But according to my df-h command, it looked like I only have 200GB available. Why is this the case? How can I take advantage of full 400GB space?



It looks like the problem is that my /dev/mapper/centos-root is all filled up. I have inserted nearly 10,000,000 rows of data with 12 columns in PostgreSQL.



Question 3: Is this big enough to take up 50GB of space?



Thanks!



Edit: output of pvs, vgs, lvs



enter image description here










share|improve this question
















I've been inserting data into PostgreSQL DB, and got the error message:



psycopg2.OperationalError: could not extend file "base/16384/61892": No space left on device
HINT: Check free disk space


I am using CentOS 7, and I've checked some of my status on my linux machine:



df -h



enter image description here



I'm pretty new to Linux, and based on the result of my df -h command, I could see that Linux storage system works differently than Windows.



It looks like PostgreSQL is pushing to /dev/mapper/centos-root, but it has only 50 GB available.



Question 1: How can I change it? How can I assign the extra free space that's available in /dev/mapper/centos-home to my ~/centos-root directory?



Question 2: My machine has two Hard disk, 200 GB each. But according to my df-h command, it looked like I only have 200GB available. Why is this the case? How can I take advantage of full 400GB space?



It looks like the problem is that my /dev/mapper/centos-root is all filled up. I have inserted nearly 10,000,000 rows of data with 12 columns in PostgreSQL.



Question 3: Is this big enough to take up 50GB of space?



Thanks!



Edit: output of pvs, vgs, lvs



enter image description here







linux centos centos7 storage postgresql






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 1 '18 at 6:05







Eric Kim

















asked Oct 1 '18 at 5:32









Eric KimEric Kim

1085




1085













  • Please post the output of pvs; vgs; lvs

    – shodanshok
    Oct 1 '18 at 5:44











  • @shodanshok please check the update. Also, what are the significance of each commands?

    – Eric Kim
    Oct 1 '18 at 6:05






  • 1





    @EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

    – HBruijn
    Oct 1 '18 at 7:15



















  • Please post the output of pvs; vgs; lvs

    – shodanshok
    Oct 1 '18 at 5:44











  • @shodanshok please check the update. Also, what are the significance of each commands?

    – Eric Kim
    Oct 1 '18 at 6:05






  • 1





    @EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

    – HBruijn
    Oct 1 '18 at 7:15

















Please post the output of pvs; vgs; lvs

– shodanshok
Oct 1 '18 at 5:44





Please post the output of pvs; vgs; lvs

– shodanshok
Oct 1 '18 at 5:44













@shodanshok please check the update. Also, what are the significance of each commands?

– Eric Kim
Oct 1 '18 at 6:05





@shodanshok please check the update. Also, what are the significance of each commands?

– Eric Kim
Oct 1 '18 at 6:05




1




1





@EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

– HBruijn
Oct 1 '18 at 7:15





@EricKim (almost) every command comes with an online manual that will give you between a hint and an encyclopaedia's worth of information on what the command does and supported switches etc.; try man pvs , man lvs and the manual for the manual system man man - but the relevant output of the command sequence shows how much of your physical disk(s) , physical volume and logical volume space is assigned and available

– HBruijn
Oct 1 '18 at 7:15










1 Answer
1






active

oldest

votes


















4














Your server is badly partitioned. This is not entirely your fault; rather, the default RHEL/CentOS settings are quite misleading in my opinion.



Let's start from the description on the pvs; vgs; lvs command entered above. They are all related to LVM2, a Logical Volume Manager which, in short, enable you to create "flexible", resizeable partitions:




  • pvs shows how the physical disks are attached to the LVM system. You had 2x 200 GB disks, but pvs only shows 1x200 GB physical device. This means your disks are in RAID1 (mirroring) and they are wholly assigned to LVM (ie: no physical space is unassigned);


  • vgs shows the Volume Group assigned to your physical devices and any usable free space. In your case free space is <4 MB, so basically you have no space free space. The next command explains what is using your space...


  • lvs shows you have two Logical Volumes (think them as partitions): a 50 GB root volume and a ~145 GB home volume. In short, your root volume (where PostgreSQL resides) is way smaller than your needs; rather, your home volume is very large considering how few data (< 5GB) it contains.



To solve the problem, you have two options:




  • relocate PostgreSQL under the home volume, for example under /home/pgsl. I would avoid this because /home is not the right place for a database and it will cause an administrative burden in the future. Moreover, you need to put SELinux into permissive mode (setenforce 0 + /etc/selinux/config editing) to let the relocation work;


  • shrink the home volume and enlarge root. This is easier said than done, especially if you are using XFS (default RHEL/CentOS filesystem), which does not support shrinking.



If and only if your data under home can be trashed / reloaded, you can follow the following steps to DELETE the home volume and enlarging root. Please note that a small error (both mine and your) WILL destroy your data (killing any cats in a ~100 KM range), and so I take NO RESPONSABILITY for the final outcome. If you are unsure, stop here and call a professional sysadmin for support. Ok, let's go ahead; I'll post a command sequence with the relative description:





  • umount /home: this unmount (ie "disable") the home volume;


  • lvremove centos/home: this permanently destroy /home and all its content;


  • lvextend centos/root -L +100G: this expand the root volume by 100 GB;


  • xfs_growfs /: assuming you are using XFS, this expand the root filesystem to match the underlying, extended volume. If you are using ext4 (which is improbable), you need to issue resize2fs /dev/centos/root.






share|improve this answer
























  • It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

    – wazoox
    Oct 1 '18 at 10:56











  • run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

    – wazoox
    Oct 1 '18 at 10:57











  • then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

    – wazoox
    Oct 1 '18 at 10:59











  • You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

    – wazoox
    Oct 1 '18 at 11:02












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f933401%2fpostgresql-could-not-extend-file-no-space-left-on-device-hint-check-free-dis%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









4














Your server is badly partitioned. This is not entirely your fault; rather, the default RHEL/CentOS settings are quite misleading in my opinion.



Let's start from the description on the pvs; vgs; lvs command entered above. They are all related to LVM2, a Logical Volume Manager which, in short, enable you to create "flexible", resizeable partitions:




  • pvs shows how the physical disks are attached to the LVM system. You had 2x 200 GB disks, but pvs only shows 1x200 GB physical device. This means your disks are in RAID1 (mirroring) and they are wholly assigned to LVM (ie: no physical space is unassigned);


  • vgs shows the Volume Group assigned to your physical devices and any usable free space. In your case free space is <4 MB, so basically you have no space free space. The next command explains what is using your space...


  • lvs shows you have two Logical Volumes (think them as partitions): a 50 GB root volume and a ~145 GB home volume. In short, your root volume (where PostgreSQL resides) is way smaller than your needs; rather, your home volume is very large considering how few data (< 5GB) it contains.



To solve the problem, you have two options:




  • relocate PostgreSQL under the home volume, for example under /home/pgsl. I would avoid this because /home is not the right place for a database and it will cause an administrative burden in the future. Moreover, you need to put SELinux into permissive mode (setenforce 0 + /etc/selinux/config editing) to let the relocation work;


  • shrink the home volume and enlarge root. This is easier said than done, especially if you are using XFS (default RHEL/CentOS filesystem), which does not support shrinking.



If and only if your data under home can be trashed / reloaded, you can follow the following steps to DELETE the home volume and enlarging root. Please note that a small error (both mine and your) WILL destroy your data (killing any cats in a ~100 KM range), and so I take NO RESPONSABILITY for the final outcome. If you are unsure, stop here and call a professional sysadmin for support. Ok, let's go ahead; I'll post a command sequence with the relative description:





  • umount /home: this unmount (ie "disable") the home volume;


  • lvremove centos/home: this permanently destroy /home and all its content;


  • lvextend centos/root -L +100G: this expand the root volume by 100 GB;


  • xfs_growfs /: assuming you are using XFS, this expand the root filesystem to match the underlying, extended volume. If you are using ext4 (which is improbable), you need to issue resize2fs /dev/centos/root.






share|improve this answer
























  • It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

    – wazoox
    Oct 1 '18 at 10:56











  • run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

    – wazoox
    Oct 1 '18 at 10:57











  • then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

    – wazoox
    Oct 1 '18 at 10:59











  • You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

    – wazoox
    Oct 1 '18 at 11:02
















4














Your server is badly partitioned. This is not entirely your fault; rather, the default RHEL/CentOS settings are quite misleading in my opinion.



Let's start from the description on the pvs; vgs; lvs command entered above. They are all related to LVM2, a Logical Volume Manager which, in short, enable you to create "flexible", resizeable partitions:




  • pvs shows how the physical disks are attached to the LVM system. You had 2x 200 GB disks, but pvs only shows 1x200 GB physical device. This means your disks are in RAID1 (mirroring) and they are wholly assigned to LVM (ie: no physical space is unassigned);


  • vgs shows the Volume Group assigned to your physical devices and any usable free space. In your case free space is <4 MB, so basically you have no space free space. The next command explains what is using your space...


  • lvs shows you have two Logical Volumes (think them as partitions): a 50 GB root volume and a ~145 GB home volume. In short, your root volume (where PostgreSQL resides) is way smaller than your needs; rather, your home volume is very large considering how few data (< 5GB) it contains.



To solve the problem, you have two options:




  • relocate PostgreSQL under the home volume, for example under /home/pgsl. I would avoid this because /home is not the right place for a database and it will cause an administrative burden in the future. Moreover, you need to put SELinux into permissive mode (setenforce 0 + /etc/selinux/config editing) to let the relocation work;


  • shrink the home volume and enlarge root. This is easier said than done, especially if you are using XFS (default RHEL/CentOS filesystem), which does not support shrinking.



If and only if your data under home can be trashed / reloaded, you can follow the following steps to DELETE the home volume and enlarging root. Please note that a small error (both mine and your) WILL destroy your data (killing any cats in a ~100 KM range), and so I take NO RESPONSABILITY for the final outcome. If you are unsure, stop here and call a professional sysadmin for support. Ok, let's go ahead; I'll post a command sequence with the relative description:





  • umount /home: this unmount (ie "disable") the home volume;


  • lvremove centos/home: this permanently destroy /home and all its content;


  • lvextend centos/root -L +100G: this expand the root volume by 100 GB;


  • xfs_growfs /: assuming you are using XFS, this expand the root filesystem to match the underlying, extended volume. If you are using ext4 (which is improbable), you need to issue resize2fs /dev/centos/root.






share|improve this answer
























  • It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

    – wazoox
    Oct 1 '18 at 10:56











  • run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

    – wazoox
    Oct 1 '18 at 10:57











  • then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

    – wazoox
    Oct 1 '18 at 10:59











  • You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

    – wazoox
    Oct 1 '18 at 11:02














4












4








4







Your server is badly partitioned. This is not entirely your fault; rather, the default RHEL/CentOS settings are quite misleading in my opinion.



Let's start from the description on the pvs; vgs; lvs command entered above. They are all related to LVM2, a Logical Volume Manager which, in short, enable you to create "flexible", resizeable partitions:




  • pvs shows how the physical disks are attached to the LVM system. You had 2x 200 GB disks, but pvs only shows 1x200 GB physical device. This means your disks are in RAID1 (mirroring) and they are wholly assigned to LVM (ie: no physical space is unassigned);


  • vgs shows the Volume Group assigned to your physical devices and any usable free space. In your case free space is <4 MB, so basically you have no space free space. The next command explains what is using your space...


  • lvs shows you have two Logical Volumes (think them as partitions): a 50 GB root volume and a ~145 GB home volume. In short, your root volume (where PostgreSQL resides) is way smaller than your needs; rather, your home volume is very large considering how few data (< 5GB) it contains.



To solve the problem, you have two options:




  • relocate PostgreSQL under the home volume, for example under /home/pgsl. I would avoid this because /home is not the right place for a database and it will cause an administrative burden in the future. Moreover, you need to put SELinux into permissive mode (setenforce 0 + /etc/selinux/config editing) to let the relocation work;


  • shrink the home volume and enlarge root. This is easier said than done, especially if you are using XFS (default RHEL/CentOS filesystem), which does not support shrinking.



If and only if your data under home can be trashed / reloaded, you can follow the following steps to DELETE the home volume and enlarging root. Please note that a small error (both mine and your) WILL destroy your data (killing any cats in a ~100 KM range), and so I take NO RESPONSABILITY for the final outcome. If you are unsure, stop here and call a professional sysadmin for support. Ok, let's go ahead; I'll post a command sequence with the relative description:





  • umount /home: this unmount (ie "disable") the home volume;


  • lvremove centos/home: this permanently destroy /home and all its content;


  • lvextend centos/root -L +100G: this expand the root volume by 100 GB;


  • xfs_growfs /: assuming you are using XFS, this expand the root filesystem to match the underlying, extended volume. If you are using ext4 (which is improbable), you need to issue resize2fs /dev/centos/root.






share|improve this answer













Your server is badly partitioned. This is not entirely your fault; rather, the default RHEL/CentOS settings are quite misleading in my opinion.



Let's start from the description on the pvs; vgs; lvs command entered above. They are all related to LVM2, a Logical Volume Manager which, in short, enable you to create "flexible", resizeable partitions:




  • pvs shows how the physical disks are attached to the LVM system. You had 2x 200 GB disks, but pvs only shows 1x200 GB physical device. This means your disks are in RAID1 (mirroring) and they are wholly assigned to LVM (ie: no physical space is unassigned);


  • vgs shows the Volume Group assigned to your physical devices and any usable free space. In your case free space is <4 MB, so basically you have no space free space. The next command explains what is using your space...


  • lvs shows you have two Logical Volumes (think them as partitions): a 50 GB root volume and a ~145 GB home volume. In short, your root volume (where PostgreSQL resides) is way smaller than your needs; rather, your home volume is very large considering how few data (< 5GB) it contains.



To solve the problem, you have two options:




  • relocate PostgreSQL under the home volume, for example under /home/pgsl. I would avoid this because /home is not the right place for a database and it will cause an administrative burden in the future. Moreover, you need to put SELinux into permissive mode (setenforce 0 + /etc/selinux/config editing) to let the relocation work;


  • shrink the home volume and enlarge root. This is easier said than done, especially if you are using XFS (default RHEL/CentOS filesystem), which does not support shrinking.



If and only if your data under home can be trashed / reloaded, you can follow the following steps to DELETE the home volume and enlarging root. Please note that a small error (both mine and your) WILL destroy your data (killing any cats in a ~100 KM range), and so I take NO RESPONSABILITY for the final outcome. If you are unsure, stop here and call a professional sysadmin for support. Ok, let's go ahead; I'll post a command sequence with the relative description:





  • umount /home: this unmount (ie "disable") the home volume;


  • lvremove centos/home: this permanently destroy /home and all its content;


  • lvextend centos/root -L +100G: this expand the root volume by 100 GB;


  • xfs_growfs /: assuming you are using XFS, this expand the root filesystem to match the underlying, extended volume. If you are using ext4 (which is improbable), you need to issue resize2fs /dev/centos/root.







share|improve this answer












share|improve this answer



share|improve this answer










answered Oct 1 '18 at 7:24









shodanshokshodanshok

26.8k34788




26.8k34788













  • It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

    – wazoox
    Oct 1 '18 at 10:56











  • run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

    – wazoox
    Oct 1 '18 at 10:57











  • then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

    – wazoox
    Oct 1 '18 at 10:59











  • You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

    – wazoox
    Oct 1 '18 at 11:02



















  • It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

    – wazoox
    Oct 1 '18 at 10:56











  • run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

    – wazoox
    Oct 1 '18 at 10:57











  • then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

    – wazoox
    Oct 1 '18 at 10:59











  • You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

    – wazoox
    Oct 1 '18 at 11:02

















It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

– wazoox
Oct 1 '18 at 10:56





It would be at least prudent to first have a look at what /home contains before nuking it, and recreate /home and remount it afterwards else problems will probably occur later...

– wazoox
Oct 1 '18 at 10:56













run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

– wazoox
Oct 1 '18 at 10:57





run "ls -l /home" and "du -sh /home/*" before destruction (and regrets.

– wazoox
Oct 1 '18 at 10:57













then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

– wazoox
Oct 1 '18 at 10:59





then "lvcreate -L10G centos home", "mkfs.xfs /dev/centos/home", mount "/home"

– wazoox
Oct 1 '18 at 10:59













You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

– wazoox
Oct 1 '18 at 11:02





You'll probably need to recreate the user home directory you're using to log into the system (because YOU MUST NOT LOGIN AS ROOT). "cp -r /etc/skel /home/user && chown -R user:users /home/user"

– wazoox
Oct 1 '18 at 11:02


















draft saved

draft discarded




















































Thanks for contributing an answer to Server Fault!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f933401%2fpostgresql-could-not-extend-file-no-space-left-on-device-hint-check-free-dis%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

Список ссавців Італії Природоохоронні статуси | Список |...

Українські прізвища Зміст Історичні відомості |...