So the ls | wc should come out to 1001 (or 1002?) I'll try it on my system and see what comes out.
On Fri, Nov 19, 2010 at 3:51 PM, Brian Stamper <[email protected]> wrote: > > I took your script and did the following with it: > > for x in {1..10}; do > > for i in {1..10000} > > do > # echo This is a test file > $i.txt > mv $i.txt $i.tmp > done > > echo "Halfway through pass $x" > > ls | wc -l > ls | sort -u | wc -l > > sleep 2 > > for i in {1..10000} > > do > # echo This is a test file > $i.txt > mv $i.tmp $i.txt > done > > echo "Done with pass $x" > > ls | wc -l > ls | sort -u | wc -l > > sleep 2 > > done > > After 10 passes, there is no difference between “ls | wc –l” and “ls | sort > –u | wc –l”. I also bumped up the number of files from 1k to 10k. So I’m > still looking for a way to reliably reproduce what has been intermittent > here. > > -brian > > > > On 11/17/10 12:16 PM, "Jason Kendall" <[email protected]> wrote: > > I wrote two scripts - and actually, I was able to trigger it by just making > the files with this: > > for i in {1..1000} > do > echo This is a test file > $i.txt > done > > The second is basicly the same, just moving the file to a new name, but it > doesn't look like that is required. > > Seems any change to the directory list tables can trigger this. > > > On 10-11-17 03:11 PM, Brian Stamper wrote: > > Re: NFS duplicate filenames > What thresholds are you using to reliably reproduce the issue? We only get > periodic file deliveries, so we see this once a month or so. How many files > definitely reproduce the issue, and does their size matter or is it > specifically number? I can attempt to reproduce here against a variety of > nfs servers. > > -brian > > > On 11/17/10 12:06 PM, "Jason Kendall" <[email protected]> wrote: > > > > Just tried it on an older box I have here: 2.6.19-skas3-v9-pre9 (client) > connecting to my drobo running 2.6.22.18 (Custom) and had the same issue. > > So I am again, back to square one.. But with a second person having the > same issue. > > > On 10-11-17 02:37 PM, Brian Stamper wrote: > > > Re: NFS duplicate filenames Centos nfs4 server - 2.6.18-194.11.3.el5 > RHEL nfs3 server - 2.6.18-194.17.1.el5 > Fedora 13 client - 2.6.34.7-56.fc13.x86_64 > > I’m not registered on the Ubuntu support site, I found your issue via > google. > > -brian > > On 11/17/10 11:26 AM, "Jason Kendall" <[email protected]> wrote: > > > > > Damnit.. That means its no longer my Drobo causing the issue. > > Could you layout the clients with kernel versions please? I'd like to go > back to tracking this down. Maybe send it to me and the ticket. Your the > first person to come forward with the same issue. > > > On Wed, Nov 17, 2010 at 2:23 PM, Brian Stamper <[email protected]> wrote: > > > > > Varies actually, we’ve seen it on Fedora 13 clients connecting to a CentOS > 5.5 server via nfsv4 and those same clients connecting to RHEL 5.5 server > via nfsv3 > > -brian > > > > On 11/17/10 11:20 AM, "Jason Kendall" <[email protected] < > http://[email protected]> > wrote: > > > > > Interesting.. what is your backend? (NFS Server?) > > > On Tue, Nov 16, 2010 at 11:56 AM, Brian Stamper <[email protected] < > http://[email protected]> > wrote: > > > > > http://lists.debian.org/debian-kernel/2010/10/msg00339.html > > Did you ever find an answer for this issue? I'm running into the same > thing on Fedora 13 and yours is the only report of it I've seen. Same > situation, I have an incoming directory with thousands of files that users > attempt to mv, resulting in duplicate filenames showing up then disappearing > eventually on their own. One difference I've seen is that if I mv/rename a > file, it is listed singular, but if I rename it back, it's once again > duplicate, at least temporarily. > > If you got any further diagnosis or answers on this, I'd appreciate any > info you have. > > -brian > > > > > > > > > > > > > > > > > > > > > >
