Terminals not frozen, but won't execute certain commands

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite
1












If I open a terminal and type, lets say ll or ls, the terminal just does nothing. It isn't frozen, because I can cancel the command, but it just doesn't return the result of the command. This happens for any terminal I now open.



Certain commands work, others don't:



  • htop, pwd, cd, ps -aux -- all work

  • ll, ls and df -h -- don't work

I have killed all my user programs/terminals I had open and still no joy. I really don't want to restart the machine because it has other programs running under other users.



Is this a known issue/what can I do to fix it?



This is CentOS 7.4







share|improve this question

















  • 2




    Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
    – Ulrich Schwarz
    May 18 at 9:28






  • 2




    If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
    – ilkkachu
    May 18 at 9:28










  • serverfault.com/questions/661548/…
    – Kamaraj
    May 18 at 9:29










  • @Kamaraj checked those, doesn't seem to be them
    – user997112
    May 18 at 9:50






  • 2




    Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
    – JigglyNaga
    May 18 at 9:59














up vote
2
down vote

favorite
1












If I open a terminal and type, lets say ll or ls, the terminal just does nothing. It isn't frozen, because I can cancel the command, but it just doesn't return the result of the command. This happens for any terminal I now open.



Certain commands work, others don't:



  • htop, pwd, cd, ps -aux -- all work

  • ll, ls and df -h -- don't work

I have killed all my user programs/terminals I had open and still no joy. I really don't want to restart the machine because it has other programs running under other users.



Is this a known issue/what can I do to fix it?



This is CentOS 7.4







share|improve this question

















  • 2




    Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
    – Ulrich Schwarz
    May 18 at 9:28






  • 2




    If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
    – ilkkachu
    May 18 at 9:28










  • serverfault.com/questions/661548/…
    – Kamaraj
    May 18 at 9:29










  • @Kamaraj checked those, doesn't seem to be them
    – user997112
    May 18 at 9:50






  • 2




    Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
    – JigglyNaga
    May 18 at 9:59












up vote
2
down vote

favorite
1









up vote
2
down vote

favorite
1






1





If I open a terminal and type, lets say ll or ls, the terminal just does nothing. It isn't frozen, because I can cancel the command, but it just doesn't return the result of the command. This happens for any terminal I now open.



Certain commands work, others don't:



  • htop, pwd, cd, ps -aux -- all work

  • ll, ls and df -h -- don't work

I have killed all my user programs/terminals I had open and still no joy. I really don't want to restart the machine because it has other programs running under other users.



Is this a known issue/what can I do to fix it?



This is CentOS 7.4







share|improve this question













If I open a terminal and type, lets say ll or ls, the terminal just does nothing. It isn't frozen, because I can cancel the command, but it just doesn't return the result of the command. This happens for any terminal I now open.



Certain commands work, others don't:



  • htop, pwd, cd, ps -aux -- all work

  • ll, ls and df -h -- don't work

I have killed all my user programs/terminals I had open and still no joy. I really don't want to restart the machine because it has other programs running under other users.



Is this a known issue/what can I do to fix it?



This is CentOS 7.4









share|improve this question












share|improve this question




share|improve this question








edited Jun 8 at 22:09









Jeff Schaller

31.1k846105




31.1k846105









asked May 18 at 9:14









user997112

2974619




2974619







  • 2




    Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
    – Ulrich Schwarz
    May 18 at 9:28






  • 2




    If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
    – ilkkachu
    May 18 at 9:28










  • serverfault.com/questions/661548/…
    – Kamaraj
    May 18 at 9:29










  • @Kamaraj checked those, doesn't seem to be them
    – user997112
    May 18 at 9:50






  • 2




    Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
    – JigglyNaga
    May 18 at 9:59












  • 2




    Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
    – Ulrich Schwarz
    May 18 at 9:28






  • 2




    If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
    – ilkkachu
    May 18 at 9:28










  • serverfault.com/questions/661548/…
    – Kamaraj
    May 18 at 9:29










  • @Kamaraj checked those, doesn't seem to be them
    – user997112
    May 18 at 9:50






  • 2




    Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
    – JigglyNaga
    May 18 at 9:59







2




2




Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
– Ulrich Schwarz
May 18 at 9:28




Do you have remote file systems mounted? Certain kinds of fileserver network connection trouble look like commands hanging when accessing the unreachable mountpoint.
– Ulrich Schwarz
May 18 at 9:28




2




2




If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
– ilkkachu
May 18 at 9:28




If it's about commands trying to access the disk, then either your disk I/O is stuck, your filesystem is b0rked, or there's just a huge load on disk I/O, making everything seem stuck. If ps aux works, see if you have processes marked with status D (uninterruptible sleep / waiting for I/O).
– ilkkachu
May 18 at 9:28












serverfault.com/questions/661548/…
– Kamaraj
May 18 at 9:29




serverfault.com/questions/661548/…
– Kamaraj
May 18 at 9:29












@Kamaraj checked those, doesn't seem to be them
– user997112
May 18 at 9:50




@Kamaraj checked those, doesn't seem to be them
– user997112
May 18 at 9:50




2




2




Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
– JigglyNaga
May 18 at 9:59




Does ls always hang, or only for certain directories? Try eg ls /bin, ls /proc.
– JigglyNaga
May 18 at 9:59










1 Answer
1






active

oldest

votes

















up vote
3
down vote













It sounds like your home directory is on a NFS share or similar, and your system is having problems accessing it. So commands like ls and df are hanging as they're not able to get information from the remote filesystem.



Make sure the NFS share is actually accessible and your machine has permission to mount the share.






share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444545%2fterminals-not-frozen-but-wont-execute-certain-commands%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    3
    down vote













    It sounds like your home directory is on a NFS share or similar, and your system is having problems accessing it. So commands like ls and df are hanging as they're not able to get information from the remote filesystem.



    Make sure the NFS share is actually accessible and your machine has permission to mount the share.






    share|improve this answer

























      up vote
      3
      down vote













      It sounds like your home directory is on a NFS share or similar, and your system is having problems accessing it. So commands like ls and df are hanging as they're not able to get information from the remote filesystem.



      Make sure the NFS share is actually accessible and your machine has permission to mount the share.






      share|improve this answer























        up vote
        3
        down vote










        up vote
        3
        down vote









        It sounds like your home directory is on a NFS share or similar, and your system is having problems accessing it. So commands like ls and df are hanging as they're not able to get information from the remote filesystem.



        Make sure the NFS share is actually accessible and your machine has permission to mount the share.






        share|improve this answer













        It sounds like your home directory is on a NFS share or similar, and your system is having problems accessing it. So commands like ls and df are hanging as they're not able to get information from the remote filesystem.



        Make sure the NFS share is actually accessible and your machine has permission to mount the share.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered May 18 at 11:40









        rusty shackleford

        1,145115




        1,145115






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f444545%2fterminals-not-frozen-but-wont-execute-certain-commands%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?