-
Notifications
You must be signed in to change notification settings - Fork 524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Constant goofys crash #377
Comments
Which operation causes this? Can you reproduce a test case? |
I meet the same issue:
|
what version is this, could you try master? |
Also have this issue on the latest build version 2018/12/07 17:04:52.924861 fuse.DEBUG <-- LookUpInode 4 ecc65405-fe6a-45c4-9b72-7d4f726553cd.jpg goroutine 1165 [running]: Issue is when there are a lot of files in the bucket |
+1 |
I also have the "panic: invalid offset", occasionally, while running a |
Upon further testing: it happens, not always, but periodically, on directories with more than 1000 files.
The same directory, listed from a container based on ubuntu:18.04 never causes a crash. |
have you tried master? |
Honestly, I haven't. |
We are using goofys to mount a S3 bucket so our customer can use FTP client to upload files to S3, but goofys crashes sometimes.
goroutine 23491354 [running]: Sometimes, the error is: goroutine 92 [running]: |
I've been running into this a lot lately. It is exacerbated by running parallel scans with multiple threads and I can make it happen regularly in this use case on a relatively large bucket (~25mil files). I have used master and here's my reproduced traceback. (fuse logging and s3 logging were both turned on, but it doesn't look like they are very helpful) 2019/06/02 22:35:43.049582 fuse.DEBUG <-- ReadDir 15986854860770944332 enron85/farmer-d/discussion_threads [112. 120] goroutine 83 [running]: |
My theory is that DeRef is being called in parallel threads for the same inode when there is a lot of parallel activity going on. I'm guessing ForgetInode is being called twice from Fuse somehow? I have hacked around it for my testing (since the S3 is static) by changing DeRef to issue a warning when the link count would go < 0 on a double deref, set stale and count to 0, and return instead of doing a panic. I'm not sure what would happen if the bucket was actually being written during this. Probably nothing good, but it's good for my test use case on a readonly mount. |
I seem to still get these (2019-11-05) in mainline master. 0.22.0 But, if I run goofys -f, it doesn't seem to be fatal to the process and I can still run ls operations. |
I'm getting a consistent crash on every moderate sized upload:
The text was updated successfully, but these errors were encountered: