Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Strange CIFS, filesystem error

    Posted on

    Hello all:

    I have a strange issue with an Azure CIFS mounted filesystem. The question is not about CIFS, but how commands such as

    ls
    access the underlying filesystem:

    I can run a command that does an

    ls
    that feeds the output to a short script. For example:

    # for item in $(ls | grep Gene); do ls $item 2>&1; done
    General_Ledger_Map_Master_24_AD_20181018105322303.csv
    General_Ledger_Map_Master_24_AN_20180725101358963.csv
    
    # for item in $(ls Gene*); do ls $item 2>&1; done
    General_Ledger_Map_Master_24_AD_20181018105322303.csv
    General_Ledger_Map_Master_24_AN_20180725101358963.csv
    

    However, if I try to

    ls
    the resultant items directly, I receive an error:

    # ls General_Ledger_Map_Master_24_AD_20181018105322303.csv
    ls: cannot access General_Ledger_Map_Master_24_AD_20181018105322303.csv: No such file or directory
    

    I thought that perhaps there were special characters in the filename but this wasn't the case:

    # ls -1b Gen*
    General_Ledger_Map_Master_24_AD_20181018105322303.csv
    General_Ledger_Map_Master_24_AN_20180725101358963.csv
    General_Ledger_Map_Master_24_AN_20180725101516770.csv
    

    Adding a wildcard to the end of the filename allows it to work:

    # ls General_Ledger_Map_Master_24_AD_20181018105322303.csv*
    General_Ledger_Map_Master_24_AD_20181018105322303.csv
    # ls General_Ledger_Map_Master_24_AD_20181018105322303.csv
    ls: cannot access General_Ledger_Map_Master_24_AD_20181018105322303.csv: No such file or directory
    

    I tried a find by inum:

    [root@hostname dirname]# ls -i Gen*
    15658490612687044608 General_Ledger_Map_Master_24_AD_20181018105322303.csv
    14359759297708032000 General_Ledger_Map_Master_24_AN_20180725101358963.csv
    

    But received this:

    [root@hostname dirname]# find . -inum 15658490612687044608
    find: util.c:294: get_info: Assertion `p->st_ino' failed.
    Aborted (core dumped)
    

    (There's a bugzilla open for this error).

    The underlying issue is with Azure and not with RHEL, but I'm curious why there's a difference between the two

    ls
    commands with and without the wildcard.

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat