"We are excited to announce that the iRODS User Group Meeting 2022 will take place July 5-8 in Leuven, Belgium! We invite you to join us and our host KU Leuven to learn how iRODS is shaping the future of data management. Registration is coming soon!
The iRODS UGM 2022 will feature multiple sessions of talks, demos, interactive discussions, and networking opportunities. To kick off the event, the iRODS Consortium Development Team will provide Beginner and Advanced Training sessions. On the last day of the UGM, we will hold an informal troubleshooting session to allow users the chance to participate in conversations with the entire core development staff about their current or planned deployments."

"This talk introduces a new iRODS backend for MinIO, a scalable, secure, S3-compatible object storage for cloud users. The iRODS backend to MinIO allows users to configure their iRODS login to access their restricted data or anonymous access to public/shared data with an iRODS Ticket. By integrating with MinIO, iRODS users can leverage the user-friendly mode of data access provided by the MinIO user interface and the MinIO object store REST API."

"Faster for lots of small files."

"Want to learn more about what the #eResearchNZ community does? Join on Feb. 10 at 6 p.m. ET / Feb. 11 at 12 p.m. NZDT to hear David Fellinger’s #iRODS discussion “Data Management Technology Driven and Sustained by the eResearch Community”.

"Several years ago, the entire process of data management and collaboration could only be performed with the use of proprietary software products that were expensive to license. To maintain a collection, data sites required a file system, hierarchical storage management system, and some means of sharing the data over several geographically diverse sites using purchased software, often from a single vendor to ensure compatibility. Data site managers were placed in a difficult position, facing quickly growing data capacity and transmission demands with limited budgets. Constraints from funding agencies and governments became very difficult, if not impossible, to manage and audit.
The iRODS (Integrated Rule-Oriented Data System) Consortium was started as an open-source software development organization in 2013 by members of the research and storage communities. The technology has roots from an earlier project started in 1995. The Consortium was launched as a response to a major scale increase in management and storage needs driven by the advent of "big data". The member community is now comprised of over 30 members and spans the globe from the Australia to Japan and much of the EU. Recent innovations as a result of community requirements will be discussed, including graphical interfaces and methods to ensure data persistence and replication management. In addition, partnerships will be discussed with Globus and others to enable large scale collaboration. Today, worldwide, FAIR discovery and directed dissemination of HPC results are being accomplished in sites controlling tens of petabytes of data with this open-source technology."

"maximum_size_of_delay_queue_in_bytes should be added to the advanced_settings of server_config.json on upgrade if not already present. It should have a default value of 0 (unlimited)."

"After imeta grows support for the admin mode option (-M), the subcommand adda will not be needed because imeta -M add accomplishes the same thing."

"Removing unused AVUs is an admin-level operation, as it affects an entire zone. Rodsusers cannot invoke this operation via the iadmin command because it is protected by the API lookup routines. However, a rodsuser can invoke the operation via irule and msiDeleteUnusedAVUs()."

"GenQuery should be exactly like SQL, but without needing to specify any tables.

"To resolve this issue, we have to claim that the requirement is part of the design, or we lift the requirement so that the last stream to close is responsible for updating the catalogue and triggering policy."

"And arguably, the storage tiering framework should drop some of those NOTICE messages to DEBUG... it's very talkative at the moment."

"Should an administrator get into this situation, iinit can be run as usual and the password entered to generate the.irodsA file again after waiting for the connection to fail. The server can then be restarted and things will return to normal."

"This will make it appear correctly to ips for the iRODS administrator."

"It is possible for NFSRODS to present incorrect information when operations are executed very quickly.
NFS detects changes in the filesystem via the mtime. iRODS stores timestamps in seconds. Systems depending on these timestamps will not operate correctly if operations complete within the same second."

"Commit 318663d makes running the docker image without the -i flag crash immediately, as /dev/stdin is absent. This makes a container workflow completely useless."

"The main branch of the irods/irods repo is out of sync with this repo."

"Once irods/irods#6156 is merged, you can re-enable/uncomment the lines mentioned above."

"I've just tried to build 4-2-stable non-package-install.... and it almost worked."
I haven't tried building the icommands via run_in_place for 4.2.11, so say on this issue if you have, and it doesn't work. If not, it's likely affecting what 4-2-stable branch, so should be fixed by 4.2.12 is released.

"I recommend looking at 4.2.11 documentation - it's mostly the same as 4.2.3 (linked), but some things have moved.
make sure you're building the 4-2-stable branch (git checkout 4-2-stable)
you can try make server first.. 
this subset of targets are the requirements for the irods-server. 
additional plugins may require some of the other make targets."

"We do not allow underscores in group names, only lowercase letters, numbers and hyphens. The datamanager group always has the same name as the category. When the category name contains an underscore the option to create a datamanager group is removed, because the datamanager group would be invalid."