[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
st_nlink=2 and no subdirs? isn't that normal?
From: |
Linda A. Walsh |
Subject: |
st_nlink=2 and no subdirs? isn't that normal? |
Date: |
Mon, 22 Jul 2013 02:50:52 -0700 |
User-agent: |
Thunderbird |
find: WARNING: Hard link count is wrong for `.' (saw only st_nlink=2 but
we already saw 0 subdirectories): this may be a bug in your file system
driver. Automatically turning on find's -noleaf option. Earlier
results may have failed to include directories that should have been
searched.
I had a CIFS volume network mounted on my local linux system and got the
above error.
On a local file system (XFS), I create a dir, 'xxx', and look to see the
link count at 2 with 0
subdirectories.
Isn't that normal?
So if there is a problem that find detected, what would it be? Should
it be something that
the CIFS people should fix? To be clear, I am running find on a linux
3.9.8-vanilla kernel,
using:
find --version
find (GNU findutils) 4.5.10
Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION CBO(level=2)
and mounting a remote file system running on a windows 7 machine.
If the bug is in the CIFS driver, what should they look for to fix?
Thanks,
Linda
- st_nlink=2 and no subdirs? isn't that normal?,
Linda A. Walsh <=