clri(8) on Solnix vs Linux and the BSDs
On Solnix, clri is the illumos /usr/sbin/clri, which zeroes one inode on a file system. It takes -F FSType and -V options and exactly one i-number, where the FreeBSD, OpenBSD and NetBSD pages show no options and accept several inode numbers.
The manual pages
- Solnix: clri(8) from
pkgs.solnix.illumos-world-man· illumos.org - FreeBSD: clri(8) 15.1-RELEASE
- OpenBSD: clri(8) 8.0
- NetBSD: clri(8) 11.0
What Solnix runs
A default Solnix system runs the illumos clri at /usr/sbin/clri. The same page documents dcopy, a symbolic link to clri with the same synopsis. No other variants are shipped.
Differences
| Compared with | Topic | What differs |
|---|---|---|
| FreeBSD, OpenBSD, NetBSD | options | Solnix clri accepts -F FSType and -V. The FreeBSD, OpenBSD and NetBSD synopses show no options at all, so scripts that pass -F or -V will not work on the BSDs.Source: Solnix clri(8) SYNOPSIS, OPTIONS -F, -V; FreeBSD/OpenBSD/NetBSD clri(8) SYNOPSIS |
| FreeBSD, OpenBSD, NetBSD | number of inodes per call | Solnix synopsis takes a single i-number after special. The BSD synopses take 'inode_number ...', so one BSD call can clear several inodes. Source: Solnix clri(8) SYNOPSIS (special i-number); FreeBSD/OpenBSD/NetBSD clri(8) SYNOPSIS (inode_number ...) |
| FreeBSD, OpenBSD, NetBSD | file system type selection | Solnix needs the FSType given with -F, or found by matching special against /etc/vfstab, or from /etc/default/fs. The BSD pages mention no FSType selection or such files.Source: Solnix clri(8) OPTIONS -F; FreeBSD/OpenBSD/NetBSD clri(8) DESCRIPTION |
| FreeBSD, OpenBSD, NetBSD | dry run with -V | Solnix clri -V echoes the full command line, built from the arguments and /etc/vfstab data, without running it. The BSD pages document no dry-run option.Source: Solnix clri(8) OPTIONS -V; FreeBSD/OpenBSD/NetBSD clri(8) SYNOPSIS |
| FreeBSD, OpenBSD, NetBSD | obsolescence and open files | The BSD pages say clri is obsoleted for normal repair work by fsck(8), and BUGS warns that if the file is open, the clri change is lost when the inode cache is written back. The Solnix page has neither statement. Source: FreeBSD/OpenBSD/NetBSD clri(8) DESCRIPTION, BUGS; Solnix clri(8) DESCRIPTION, NOTES |
| FreeBSD, OpenBSD, NetBSD | warning about directory entries | The Solnix page warns that zeroing an inode that still has a directory entry leaves a stale entry. When the inode is reused, removing the old entry destroys the new file. The BSD pages give no such warning. Source: Solnix clri(8) DESCRIPTION; FreeBSD/OpenBSD/NetBSD clri(8) DESCRIPTION |
| FreeBSD, OpenBSD, NetBSD | FSType support | Solnix notes that clri might not be supported for all FSTypes. The BSD pages do not discuss file system types. Source: Solnix clri(8) NOTES; FreeBSD/OpenBSD/NetBSD clri(8) DESCRIPTION |
| FreeBSD, OpenBSD, NetBSD | large files | The Solnix page refers to largefile(7) for behaviour with files of 2 Gbyte (2^31 bytes) or more. The BSD pages say nothing on this. Source: Solnix clri(8) USAGE; FreeBSD/OpenBSD/NetBSD clri(8) |
Standards
- POSIX: clri is not a POSIX.1-2024 utility.
Writing portable scripts
- Call clri as 'clri special inode' with a single inode number and no options. Loop over inodes if you need several, and run fsck afterwards on every system.
Every difference here is taken from the manual pages linked above: Solnix's published page, Linux (man-pages and the GNU and util-linux manuals), FreeBSD, OpenBSD and NetBSD. Each row names its source. Where a manual is silent, this page is too. Compiled 2026-10-26. Found a mistake? Mail hackers@lists.solnix.io.