Just to add a bit of complexity, the number depends on the filesystem
used. While true for an ext* filesystem that the number reflects the count
of the number of folders within a directory, including the pointers to its
parent and itself ( .. and . ), that may not be true on other filesystems,
more importantly, doing
mkdir foo
ls -la foo
will show all the files in the newly created directory
That should be 2 namely . and ..
so 3,4, or 5 indicates you have that many directory entries.
lf "ls foo" shows nothing then there are 5 files starting with a dot.
so 3 more than just . and ..
On Sun, 6 Feb 2022, Reid wrote:
That's the number of hard links. See section 10.1.2 of `info ls`.
Ah, yes. That's familiar from a very long time ago that I had since
forgotten.
Thanks,
Rich
On Sun, 6 Feb 2022, Reid wrote:
That isn't lsattr; that's ll.
The only attribute on each directory is 'e'.
Rich
On Sun, 6 Feb 2022, Reid wrote:
What do you mean when you say it won't initialize? What happens when you
try?
Reid,
Dirvish, the backup software I use, needs a copy of the current contents of
a partition in the vault (the backup directory) so changes can be tracked
during daily runs. When I
On Sun, 6 Feb 2022, Reid wrote:
That's the number of hard links. See section 10.1.2 of `info ls`.
Reid,
So that should not affect being able to write to the directory. Wonder why
the one is different from the others as they were all created manually and
sequentially.
Thanks,
Rich
In /mnt/backup there are six vaults; I've initialized five of them;
salmo-data2/ won't initialize.
When I look at the long output of ls for that directory I see that five
vaults have the number 4 immediately following the perms, but salmo-data2/
has the number 5:
# ll
total 40
drwx-- 2 root