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

Error: [Errno 30] Read-only file system: '/cvmfs/dunedaq.opensciencegrid.org/spack/externals/ext-v1.0/spack-0.18.1-gcc-12.1.0/spack-0.18.1/opt/spack/gcc-12.1.0/py-pip-21.3.1-pa5nzg65cqus4bpxn4qjiuww46xsmlvj/lib64' #33

Open
estevezalonsopablougr opened this issue Sep 12, 2023 · 0 comments

Comments

@estevezalonsopablougr
Copy link

Hello, my name is Pablo and I met this issue executing dbt-setup-release fddaq-v4.1.1 after source /cvmfs/dunedaq.opensciencegrid.org/setup_dunedaq.sh and setup_dbt latest. Of course, I can access to the corresponding areas on CernVM-FS through its package cvmfs and I have the corresponding repositories mounted on my computer (and I can explore them). But, the most curious part of this is that file does not exist, at least, on my computer (Almalinux 9.2 on a VM Oracle). Let me explain, if I list the directory ls /cvmfs/dunedaq.opensciencegrid.org/spack/externals/ext-v1.0/spack-0.18.1-gcc-12.1.0/spack-0.18.1/opt/spack/gcc-12.1.0/py-pip-21.3.1-pa5nzg65cqus4bpxn4qjiuww46xsmlvj/lib64, the command line provides me the classic answer when a file or directory does not exist: ls: no se puede acceder a '/cvmfs/dunedaq.opensciencegrid.org/spack/externals/ext-v1.0/spack-0.18.1-gcc-12.1.0/spack-0.18.1/opt/spack/gcc-12.1.0/py-pip-21.3.1-pa5nzg65cqus4bpxn4qjiuww46xsmlvj/lib64': No existe el fichero o el directorio (Sorry for the Spanish, nevertheless you can translate it easily). That is the problem I have.

Then, does anyone know what is happening? Is there a problem in my access configuration to CernVM-FS? Do I get the wrong version of any package (I follow strictly the instrucctions of daq-buildtools updated at 10 August 2023)?

Do not be afraid of request me any further information about the context of the problem or any complain about the exposition of this issue to clarify better the problem. Thank you so much for your attention, I wait your answers.

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

No branches or pull requests

1 participant