mke2fs returns return code 130. Why is it returned?

Solution Verified - Updated -

Issue

  • mke2fs returns return code 130. Why is it returned?
    sample log

     [root@example-server ~]# mke2fs -j /dev/VolGroup/lvol01
     mke2fs 1.39 (29-May-2006)
     Filesystem label=
     OS type: Linux
     Block size=4096 (log=2)
     Fragment size=4096 (log=2)
     51380224 inodes, 102759424 blocks
     5137971 blocks (5.00%) reserved for the super user
     First data block=0
     Maximum filesystem blocks=4294967296
     3136 block groups
     32768 blocks per group, 32768 fragments per group
     16384 inodes per group
     Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
        102400000
    
     Writing inode tables:    0/3136   1/3136   2/3136   ...<skip>...
     Creating journal (32768 blocks): done
     Writing superblocks and filesystem accounting information: 
     [root@example-server ~]# echo $?
     130
    

Environment

  • Red Hat Enterprise Linux 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.