Replies: 7 comments 1 reply
-
input/output errror usually occurs when the object storage fails to be read. |
Beta Was this translation helpful? Give feedback.
-
Thanks for your reply.
I have checked the path |
Beta Was this translation helpful? Give feedback.
-
You may have enabled the |
Beta Was this translation helpful? Give feedback.
-
You are right. I deleted the cache files in Another question I have is why does this error occur? How can I avoid it as much as possible? |
Beta Was this translation helpful? Give feedback.
-
Read the documentation mentioned above for details |
Beta Was this translation helpful? Give feedback.
-
I need to write a cache. How should I set it up to ensure that it can upload complete data? |
Beta Was this translation helpful? Give feedback.
-
Is there any command to force synchronization? |
Beta Was this translation helpful? Give feedback.
-
I created a juicefs file system. It is used for persistent storage of pods in k8s.
![image](https://private-user-images.githubusercontent.com/9190516/360362794-6bbf2b07-d737-40ac-9ac1-63434e54366b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MzcxMzcsIm5iZiI6MTczODgzNjgzNywicGF0aCI6Ii85MTkwNTE2LzM2MDM2Mjc5NC02YmJmMmIwNy1kNzM3LTQwYWMtOWFjMS02MzQzNGU1NDM2NmIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDZUMTAxMzU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZWE0NzNjMjRkNWE3OTI3ZWYxMjkwMTY3ZjcyZWQxZTQ0MTM1MDJjYTA3Y2FmYmU5OWI3NjAxMDIyNDYxZmI1NCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.SfjSkA-T7mLoUWDJT8OTdyHti7OPRXUDQNKVG0XtN-o)
I encountered a strange problem:
When I directly mounted juicefs in VM (
juicefs mount -d "mysql://juicefs@(172.x.x.x:3306)/juicefs" /mnt/k8sjfs
), all files can be read normally.However, when I mounted the same path to pod through pv, most of the files can be read normally, but some files cannot be read. When viewing the file, an error is reported: Input/output error
![image](https://private-user-images.githubusercontent.com/9190516/360363582-ff2ee060-f381-478a-8caa-8333bb6e64df.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MzcxMzcsIm5iZiI6MTczODgzNjgzNywicGF0aCI6Ii85MTkwNTE2LzM2MDM2MzU4Mi1mZjJlZTA2MC1mMzgxLTQ3OGEtOGNhYS04MzMzYmI2ZTY0ZGYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDZUMTAxMzU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjVhNTU4MDI5YWMxNWMyNzE5YzY2MGFmZjVkZWJhZjljMjAwOGRmNzc1NjA4ZjliMGQ3NGMyNDI2Yjc4MGFmYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.UXt0wg1nU-yqYXaHtw2QjCrVlMpFxUgp9kK2N5JhgIY)
I tried a few possible solutions:
Delete and rebuild the mount pod, the problem still exists.
Start the pod on another node, and the problem still exists.
juicefs version is the same.
![image](https://private-user-images.githubusercontent.com/9190516/360366378-e8b7b34b-8340-42e9-939f-64e6bd008bf3.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MzcxMzcsIm5iZiI6MTczODgzNjgzNywicGF0aCI6Ii85MTkwNTE2LzM2MDM2NjM3OC1lOGI3YjM0Yi04MzQwLTQyZTktOTM5Zi02NGU2YmQwMDhiZjMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDZUMTAxMzU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ODdiMjlhNGRmNjJiYjFhYjZjMjcyZWE4MTFmN2M4YjU5MjIxMzRmNDFiNGYyNTgyYmE3NTk1Y2JjOTYwOTY1ZSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.T14VBIW4OBDeGd9XVDQzzcknbOr-q1-v3pdtLy5LqvE)
Change a pod image, the problem still exists.
![image](https://private-user-images.githubusercontent.com/9190516/360363976-ceef88e0-de04-4c3a-b387-d1cd597c1b97.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MzcxMzcsIm5iZiI6MTczODgzNjgzNywicGF0aCI6Ii85MTkwNTE2LzM2MDM2Mzk3Ni1jZWVmODhlMC1kZTA0LTRjM2EtYjM4Ny1kMWNkNTk3YzFiOTcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDZUMTAxMzU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDE3NTc2MWU3NmU0ZDYzODQ4ZjhiN2M1Mzk0OWJiMDUxOTg3MzJmYzMwNjliMGNiNWI5ZmE5NDM5NWQzYjA4YyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.fIlbawzzP0JYp_ErBaBB3ZreDleT0O72Hj3v-AzyocE)
In the same path, a new file can be read normally.
![image](https://private-user-images.githubusercontent.com/9190516/360365203-b5f51e0d-5268-42b9-a984-fec3bac4a44c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4MzcxMzcsIm5iZiI6MTczODgzNjgzNywicGF0aCI6Ii85MTkwNTE2LzM2MDM2NTIwMy1iNWY1MWUwZC01MjY4LTQyYjktYTk4NC1mZWMzYmFjNGE0NGMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDZUMTAxMzU3WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NjAzOGMyYzM5NDg2Mjg1MmVlOWZmNzdmZmNlZmM1NmJhMTY2MjNiMTAwYmIyMzMzZWU2ZGYwNGFjYzU5NDdhMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.gj1EQ7bYq5YBEFIMSaHceDoV32_dB6FNz3dsm_NL6yQ)
According to my attempts, I can solve this problem by rebuilding the problematic files. However, this is not a good solution. Because I don't know when this problem will occur again.
Moreover, the problematic file looks no different from other files in the VM.
I haven't found the same problem in the issues and discussions history, and I don't know how to solve this problem completely. I hope to get some troubleshooting ideas. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions