LittleFlower2019 / s3fs

Automatically exported from code.google.com/p/s3fs
GNU General Public License v2.0
0 stars 0 forks source link

make check failing inconsistently #363

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Detailed description of observed behavior:

make  check-TESTS
make[2]: Entering directory `/home/matt/development/s3fs-1.72/test'
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
echo HELLO WORLD to test-s3fs.txt
Verifying length of test file
error: expected 15 , got 10
FAIL: small-integration-test.sh

The error is inconsistent in that sometimes I will have 10 lines like above, 
sometimes one more or one less.

Dropping back to version 1.71 tests without issue.

===================================================================
The following information is very important in order to help us to help
you.  Omission of the following details may delay your support request or
receive no attention at all.
===================================================================
Version of s3fs being used (s3fs --version): 1.72

Version of fuse being used (pkg-config --modversion fuse): 2.9.2-4

System information (uname -a): Linux work 3.10-2-amd64 #1 SMP Debian 3.10.7-1 
(2013-08-17) x86_64 GNU/Linux

Distro (cat /etc/issue): Debian GNU/Linux jessie/sid

s3fs syslog messages (grep s3fs /var/log/syslog):

# grep s3fs /var/log/syslog
Aug 21 00:20:40 work s3fs: init $Rev: 461 $
root@work:/home/matt/development/s3fs-1.72#

Original issue reported on code.google.com by mst...@gmail.com on 21 Aug 2013 at 7:27

GoogleCodeExporter commented 8 years ago
Hi,

I updated new revision as r471 for this issue.

I think that the cause of this bug is fuse's calling function sequence.
Fuse does not wait finishing "release file descriptor" function called by fuse, 
and fuse runs(calls) next processing(commands).
Then s3fs could not clear stats cache information for that file before calling 
next processing, and s3fs uses old stats cache information.

But if use_cache option is specified, s3fs run no problem.
Because s3fs has file cache, and s3fs use(read/write) from this cache file.

So that, I changed codes that s3fs clears stats cache in release function at 
first.

Please check new revision(r471), and if you find other bugs please post new 
issue.
I closed this issue.

Thanks in advance for your assistance.

Original comment by ggta...@gmail.com on 22 Aug 2013 at 9:43