Re: [Help-bash] What could cause ls and echo return different files?
From:
Greg Wooledge
Subject:
Re: [Help-bash] What could cause ls and echo return different files?
Date:
Wed, 14 May 2014 12:53:25 -0400
User-agent:
Mutt/1.4.2.3i
On Wed, May 14, 2014 at 11:33:53AM -0500, Peng Yu wrote:
> I have a file system on glusterfs (http://www.gluster.org/). The
> strange thing is that the following commands can give different files.
>
> $ ls xxx.fastq.gz.*
> xxx.fastq.gz.finished xxx.fastq.gz.stdouterr
> $ echo xxx.fastq.gz.*
> xxx.fastq.gz.finished xxx.fastq.gz.lockfile xxx.fastq.gz.stdouterr
>
> Even more wired, the exact same commands may give different answers
> from time to time. This must be somehow related to glusterfs. But is
> there a way at the bash level to show what might be wrong.
Who says anything is "wrong"? If a lockfile is created temporarily
and then removed, that seems pretty normal to me.
You're looking at a live, active system. Things change. Programs may
create and remove locks, create and remove temporary storage files, and
so on.