> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-maintain-landing-page/troubleshoot-data-storage-optimizer-fs/accessing-pdso-volumes-directly.md). # Access the Data Optimizer volumes directly When necessary, you can access the Data Optimizer volume directly for troubleshooting. This might include performing directory listings, checking file status, or running the `df` command to report file system usage. In all these cases, access the volume as either the root user or as the **System User** specified in the Data Optimizer configuration. The following examples show how to directly access the volumes: 1. Attempt to access as `svcusr` user (Permission denied): Attempting to access the Data Optimizer mount as the `svcusr` user might result in a "permission denied" error. ``` [svccusr]# ls -l /ldo/mnt ls: cannot access /ldo/mnt: Permission denied d????????? ? ? ? ? ? mnt ``` 2. Successful access as `root` and `hdfs` users: * Using the `root` or `hdfs` users for the `ls` operation succeeds. * The mount is owned by the `hdfs` user and `hdfs` group, with the `hdfs` user having full `rwx` (read, write, execute) permissions, and other users in the `hdfs` group having `rx` (read, execute) permissions. ``` [svccusr]# sudo ls -l /ldo/mnt drwxr-x--- 1 hdfs hdfs 0 Aug 8 1995 dn [svccusr]# sudo -u hdfs ls -l /ldo/mnt drwxr-x--- 1 hdfs hdfs 0 Aug 8 1995 dn ``` 3. Failed access using `sudo` to the `hdfs` group: * Sudoing to the `hdfs` group might still result in a "permission denied" error when accessing the LDO mount. * Ensure you use either the root user or the owner to access Data Storage Optimizer mounted volumes. ``` [svccusr]# sudo -g hdfs ls -l /ldo/mnt ls: cannot access /ldo/mnt: Permission denied ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.pentaho.com/pdc-10.2-data-optimizer/pdso-install-landing-page/pdso-install-in-hadoop-cluster/pdso-maintain-landing-page/troubleshoot-data-storage-optimizer-fs/accessing-pdso-volumes-directly.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.