iRODS FUSE Lite

FUSE implementation of iRODS Client written in Golang

What is it?

Users are able to mount an iRODS Collection (multiple Collections or DataObjects are also available) on the directory hierarchy. Doing so, data stored on iRODS can be accessed via the directory hierarchy as if they are in local disks.

Download pre-built binaries

Pre-built binaries can be found in Release in the repository. Checkout tarballs attached as assets in a release.

iRODS FUSE Lite only works on Linux systems. MacOS (osx) is not supported as FUSE library is not open-source anymore. The binaries run on any Linux distros (e.g., Ubuntu 18.x, Ubuntu 20.x, CentOS 7, or CentOS 8) without requiring any dependencies. Use correct release binaries for your OS and architecture.

Links for iRODS FUSE Lite: https://github.com/cyverse/irodsfs/releases

Build from source

Prerequisite - libFUSE

iRODS FUSE Lite requires libFUSE library to provide file system mount in linux. libFUSE can be installed using linux package managers, such as yum or apt.

In Ubuntu,

sudo apt-get install -y fuse

In CentOS,

sudo yum install -y fuse

Prerequisite - privileged access in Docker

This only applies to users who run iRODS FUSE inside docker containers

To use libFUSE in Docker containers, users should launch the docker container in privileged mode using --privileged option.

docker run -ti --privileged <docker_image_name> /bin/bash

Prerequisite - Go

iRODS FUSE Lite is written in Go. So Go is required to build iRODS FUSE Lite. Note that once iRODS FUSE Lite is built, it does not require Go for running. To install Go, please refer official installation guide.

Prerequisite - Build essentials

To build, some common build essentials, such as Make, are required.

In Ubuntu,

sudo apt-get install -y make

In CentOS,

sudo yum install -y make

Build

Clone the source repository using git or download the zip file of the source.

Clone the source repository using git and build.

git clone https://github.com/cyverse/irodsfs
cd irodsfs
make build

Download the zip file of the source and build.

curl -L -o irodsfs.zip https://github.com/cyverse/irodsfs/archive/refs/heads/main.zip
unzip irodsfs.zip
cd irodsfs-main
make build

After successful build, you will be able to find the binary in bin directory.

How to use?

Mount an iRODS Collection using URL

An iRODS user iychoi mounts a collection /iplant/home/iychoi in iRODS Server data.cyverse.org on a local directory /mount/irods.

• iRODS User: iychoi
• iRODS Password: my_password
• iRODS Host: data.cyverse.org
• iRODS Port: 1247
• iRODS Zone: iplant
• iRODS Collection to mount: /iplant/home/iychoi
• Local directory to mount: /mount/irods

Run irodsfs.

./bin/irodsfs irods://iychoi:my_password@data.cyverse.org:1247/iplant/home/iychoi /mount/irods

After mounting, irodsfs will be executed in the background.

Test access the mount.

ls /mount/irods

Mount an iRODS Collection using a config YAML file

An iRODS user iychoi mounts a collection /iplant/home/iychoi in iRODS Server data.cyverse.org on a local directory /mount/irods.

• iRODS User: iychoi
• iRODS Password: my_password
• iRODS Host: data.cyverse.org
• iRODS Port: 1247
• iRODS Zone: iplant
• iRODS Collection to mount: /iplant/home/iychoi
• Local directory to mount: /mount/irods

Create a config.yaml file.

irods_host: data.cyverse.org
irods_port: 1247
irods_user_name: iychoi
irods_zone_name: iplant
irods_user_password: `my_password`

path_mappings:
  - irods_path: /iplant/home/iychoi
    mapping_path: /
    resource_type: dir

Then run irodsfs with --config or -c option.

./bin/irodsfs -c config.yaml /mount/irods

After mounting, irodsfs will be executed in the background.

Test access the mount.

ls /mount/irods

Mount an iRODS Collection with PAM Authentication and SSL

An iRODS user iychoi mounts a collection /iplant/home/iychoi in iRODS Server data.cyverse.org on a local directory /mount/irods with PAM Authentication (with SSL).

• iRODS User: iychoi
• iRODS Password: my_password
• iRODS Host: data.cyverse.org
• iRODS Port: 1247
• iRODS Zone: iplant
• iRODS Collection to mount: /iplant/home/iychoi
• Local directory to mount: /mount/irods
• Authentication Scheme: pam
• CA Cert File: /etc/ssl/certs/ca-certificates.crt
• Encryption Key Size: 32
• Encryption Algorithm: AES-256-CBC
• Encryption Salt Size: 8
• Hash Rounds: 16

Create a config.yaml file.

irods_host: data.cyverse.org
irods_port: 1247
irods_user_name: iychoi
irods_zone_name: iplant
irods_user_password: `my_password`

irods_authentication_scheme: "pam_password"
irods_ssl_ca_certificate_file: "/home/iychoi/.irods/ca_cert.pem"
irods_encryption_key_size: 32
irods_encryption_algorithm: "AES-256-CBC"
irods_encryption_salt_size: 8
irods_encryption_num_hash_rounds: 16

path_mappings:
  - irods_path: /iplant/home/iychoi
    mapping_path: /
    resource_type: dir

Then run irodsfs with --config or -c option.

./bin/irodsfs -c config.yaml /mount/irods

After mounting, irodsfs will be executed in the background.

Test access the mount.

ls /mount/irods

Mount multiple iRODS Collections or Data Objects

An iRODS user iychoi mounts a collection /iplant/home/iychoi/mount1 and /iplant/home/iychoi/mount2 in iRODS Server data.cyverse.org under a local directory /mount/irods.

• iRODS User: iychoi
• iRODS Host: data.cyverse.org
• iRODS Port: 1247
• iRODS Zone: iplant
• iRODS Collections to mount: /iplant/home/iychoi/mount1 and /iplant/home/iychoi/mount2
• Local directory to mount: /mount/irods

Create a config.yaml file.

irods_host: data.cyverse.org
irods_port: 1247
irods_user_name: iychoi
irods_zone_name: iplant
irods_user_password: `my_password`

path_mappings:
  - irods_path: /iplant/home/iychoi/mount1
    mapping_path: /mount1
    resource_type: dir
  - irods_path: /iplant/home/iychoi/mount2
    mapping_path: /mount2
    resource_type: dir

Then run irodsfs with --config or -c option.

./bin/irodsfs -c config.yaml /mount/irods

After mounting, irodsfs will be executed in the background.

Test access the mount.

ls /mount/irods

Mount User's iRODS Home Collection using iCommands config (~/.irods)

An iRODS user iychoi has iCommands config in ~/.irods.

Run irodsfs without any --config or -c option.

./bin/irodsfs /mount/irods

After mounting, irodsfs will be executed in the background.

Test access the mount.

ls /mount/irods

Change Log Level

An iRODS can change the log level in two ways: 1) using command-line argument --log_level or 2) using log_level parameter in a configuration file.

There are 6 log levels configurable (case-insensitive):

• "PANIC"
• "FATAL"
• "WARN"
• "INFO"
• "DEBUG"
• "TRACE"

For example, to display only fatal or more severe error logs, run irodsfs with --log_level FATAL option.

./bin/irodsfs -c ~/.irods --log_level FATAL /mount/irods

Command-line argument --log_level overrides the log level set in a configuration file if any.

To set the log level using a configuration file, add a log_level field.

irods_host: data.cyverse.org
irods_port: 1247
irods_user_name: iychoi
irods_zone_name: iplant
irods_user_password: `my_password`
log_level: FATAL

path_mappings:
  - irods_path: /iplant/home/iychoi/mount1
    mapping_path: /mount1
    resource_type: dir
  - irods_path: /iplant/home/iychoi/mount2
    mapping_path: /mount2
    resource_type: dir

Unmount

It is recommended to use fusermount command to unmount iRODS FUSE Lite as it does not require admin permission.

fusermount -u /mount/irods

It may fail unmounting with device is busy error if you have processes accessing the mount (e.g., shell). In the case, close the processes first and retry unmounting. Otherwise, you can also try lazy-unmount, which will mark to unmount after the processes using the mount are closed.

fusermount -u -z /mount/irods

It is also possible to use umount command to unmount iRODS FUSE Lite. But in this case, you will need admin permission (or sudo).

sudo umount /mount/irods

License

Copyright (c) 2010-2021, The Arizona Board of Regents on behalf of The University of Arizona

All rights reserved.

Developed by: CyVerse as a collaboration between participants at BIO5 at The University of Arizona (the primary hosting institution), Cold Spring Harbor Laboratory, The University of Texas at Austin, and individual contributors. Find out more at http://www.cyverse.org/.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
• Neither the name of CyVerse, BIO5, The University of Arizona, Cold Spring Harbor Laboratory, The University of Texas at Austin, nor the names of other contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Please check LICENSE file.