Skip to content
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

Read Only file system Not able to write into the mounted volume #8457

Open
omgupta240909 opened this issue Apr 28, 2024 · 3 comments
Open

Read Only file system Not able to write into the mounted volume #8457

omgupta240909 opened this issue Apr 28, 2024 · 3 comments

Comments

@omgupta240909
Copy link

Hi Team ,
we are using longhorn for our airflow deployments and we have total 5 intances of airflow , and we have k8s cluster of 3 master nodes and 9 worker node , and we have added 1 , 1Tb of disk to all of the worker nodes. all are working fine.

suddenly we observed that few airflow instances are gone into the read only , and not able to write into it, you can see the logs below.
image

After troubleshooting we found that in 2 worker nodes the iscsi servise is not running so we have disable the volume scheduing into that.
image

after restarting the iscsi service its not coming up.

we have manually started the aliflow instances, what is reason that it goes into the read only and how do i start my iscsi service so that a will enable the longhorn volume scheduling .

please help.

@derekbit
Copy link
Member

Your iSCSI service seems problematic and leads to IO errors in Longhorn volumes.
Can you check logs of the dmesg and iSCSI service ?

@omgupta240909
Copy link
Author

Hi @derekbit
not able to start ISCSI service on the nodes,
image

@derekbit
Copy link
Member

Hello @omgupta240909, I mean you can check the logs I mentioned to find the root cause. I think the failed iSCSI service is not caused by Longhorn.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Pending user response
Development

No branches or pull requests

2 participants