The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

FileSystem Warning

Discussion in 'General Discussion' started by fidividi, May 16, 2014.

  1. fidividi

    fidividi Active Member

    Joined:
    Feb 15, 2013
    Messages:
    43
    Likes Received:
    0
    Trophy Points:
    6
    cPanel Access Level:
    Root Administrator
    Hi,

    After a server reboot due to kernel upgrade I see below messages in /var/log/messages:

    Code:
    "EXT4-fs (sda3): warning: mounting fs with errors, running e2fsck is recommended
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (sda2): warning: checktime reached, running e2fsck is recommended
    EXT3-fs (sda2): using internal journal
    EXT3-fs (sda2): mounted filesystem with ordered data mode
    Adding 2096120k swap on /dev/sda1.  Priority:-1 extents:1 across:2096120k
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs (loop0): warning: checktime reached, running e2fsck is recommended
    EXT3-fs (loop0): using internal journal
    EXT3-fs (loop0): mounted filesystem with ordered data mode
    NET: Registered protocol family 10
    
    EXT4-fs error (device sda3): ext4_mb_generate_buddy: EXT4-fs: group 3: 510 blocks in bitmap, 507 in gd
    EXT4-fs error (device sda3): ext4_mb_generate_buddy: EXT4-fs: group 5: 510 blocks in bitmap, 509 in gd
    JBD: Spotted dirty metadata buffer (dev = sda3, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
    JBD: Spotted dirty metadata buffer (dev = sda3, blocknr = 0). There's a risk of filesystem corruption in case of system crash."
    My system is an active and sensitive machine which I can not risk any down-time. What is the best way to go about above errors and get them resolved? Are they serious?

    Thank you.
     
  2. vanessa

    vanessa Well-Known Member
    PartnerNOC

    Joined:
    Sep 26, 2006
    Messages:
    817
    Likes Received:
    22
    Trophy Points:
    18
    Location:
    Virginia Beach, VA
    cPanel Access Level:
    DataCenter Provider
    You need to run a fsck against the filesystem - there is no way around this on your current server.

    How to FSCK a Linux Filesystem :: The cPanel Admin

    If you don't want downtime, your only other option is to migrate to another server, even just temporarily to let the repair run. If you don't fsck your filesystem, it will eventually start going read-only and require a reboot until it's fixed.

    In the future, be mindful of how you reboot. These things happen, but more often than not due to abrupt reboots (ie, power cycling the server instead of shutting it down)
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    You will not be able to resolve the issue without some temporarily downtime, as Vanessa mentioned. Note that if you are not comfortable using FSCK, it might be a good idea to consult with your data center or a qualified system administrator.

    Thank you.
     
Loading...

Share This Page