1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

/boot sector increased hugely overnight

Discussion in 'General Discussion' started by tank, Mar 5, 2012.

  1. tank

    tank Member

    Joined:
    Apr 12, 2011
    Messages:
    209
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Chicago, IL
    My question to all of you smart people out their, is why would my put sector increase by 21% in one day.

    As of 2/17/2012 till now
    /dev/sda1 342M 100M 225M 31% /boot

    As before then:
    /dev/sda1 342M 29M 297M 9% /boot

    I know this is a very vague question but I am hoping that their is some obvious answer. If you need more information please let me know and I will happily provide it. Thanks for the help

    Edit**
    Would optimizing my MySQL do this?
    Tank
     
  2. tank

    tank Member

    Joined:
    Apr 12, 2011
    Messages:
    209
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Chicago, IL
    Thanks taking a look at those. So basically i have another kernel sitting on the machine. So I looked at the instructions I am still missing something.

    Code:
    By seahorse
    
    1: rm -f /var/lib/rpm/__*
    
    2: uname -a
    check your current kernel
    
    3: rpm -aq | grep kernel-*
    list out kernels in your system and remember those that you do not need
    
    4: rpm --rebuilddb 
    rebuild rpmdb 
    
    5: rpm -e [kernel file to be removed] 
    remove those unused kernels to free the /boot/ space
    My questions is what goes in the first step to. he left that "_" their. This blank is holding me up. Plus can anyone tell a noob at linux what step 4 does for the process.

    Thanks for the info, learning every day.
     
  3. cPanelTristan

    cPanelTristan Active Member
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,621
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    Hello,

    The __ portion is how the rpm database files are named. I wouldn't suggest removing those files but moving them:

    Code:
    mv /var/lib/rpm/__db* /root
    Also, you can always cd to a directory and list the file contents to clear up any confusion on naming conventions going forward:

    Code:
    cd /var/lib/rpm
    ls -lah
    That would have likely made everything clearer for you :)

    As for step 4, it rebuilds the rpm database that you moved in Step 1.

    Thanks!
     
  4. tank

    tank Member

    Joined:
    Apr 12, 2011
    Messages:
    209
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Chicago, IL
    Ok cool thanks. Why would I want to move the RPM and then rebuild them. What is the benefit in that? Is this good for servers?
     
  5. cPanelTristan

    cPanelTristan Active Member
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,621
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    I wouldn't have recommended doing it myself, so I cannot answer that question. I don't frankly feel it's a necessary step to move the rpm database at all unless yum isn't working for you.
     

Share This Page