IBM Support

IV80593: MKFS COMMAND DOES NOT PRINT AN ERROR MESSAGE APPLIES TO AIX 7100-03

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The mkfs command is not able to print
any error messages if it fails to complete
successfully.  For example, if one tries
to use mkfs to create a loopmount file
system, but mounts the file system where
the loopmount file resides read-only, then
the mkfs command should fail and should
print an error message.  But actually it
prints nothing and just exits with an
error code of 5 (EIO):
# mkfs -V jfs2 -o log=INLINE /dev/loop0
mkfs: destroy /dev/loop0 (yes)? yes

# echo $?
5

Local fix

  • N/A

Problem summary

  • no error messages from mkfs

Problem conclusion

  • fix an error definiton

Temporary fix

  • 



Comments


    

  • 



APAR Information




    

  • APAR number
    IV80593
    • 

  • Reported component name
    AIX V7.1
    • 

  • Reported component ID
    5765H4000
    • 

  • Reported release
    710
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt / Xsystem
    • 

  • Submitted date
    2016-01-20
    • 

  • Closed date
    2016-04-11
    • 

  • Last modified date
    2017-01-20
    • 





    

  • APAR is sysrouted FROM one or more of the following:
    

    • 

  • APAR is sysrouted TO one or more of the following:
    

    
IV83543 IV83585 IV83707 IV88045
    

    • 



Fix information


    

  • Fixed component name
    AIX V7.1
    • 

  • Fixed component ID
    5765H4000
    • 



Applicable component levels


    

  • R710  PSY  U872336
       UP17/01/19  I  1000
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SG11R"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]
              

                                                                    

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            19 April 2022
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback