Linux Storage Access & Ownership

I needed an application workspace on an already-mounted drive to be writable by my normal Linux account. Hermes could read the volume but could not initially write to the workspace.

Hermes reported that the drive was mounted and identified its operating account. I created a dedicated application directory rather than changing ownership across the whole volume.

I changed the directory's user owner to my account. The recorded chown command did not change the group, which remained root; the alternative owner-and-group change was only discussed.

I created a test file as the normal user, without sudo, and confirmed that the write succeeded. This tested the application's needed access rather than merely whether an administrator could write there.

I made a dedicated workspace on the mounted drive writable by my normal account and confirmed it with a successful non-root write test.

The saved September 30 lab preserves directory creation, the user-owner change, and the write-test command, followed by my success confirmation.

This record does not establish partitioning, formatting, a filesystem UUID, an fstab entry, or mounting after reboot. Suggested mount inspections are not counted as completed checks.

I learned that a readable mount can still need a directory ownership change before an application can write to it.

I practiced separating user ownership from group ownership, and write access from mount persistence or drive health.