nilfs_sufile_truncate_range(9)

✨ nilfs_sufile_truncate_range ✨

okay so bestie, this one is from the Kernel API Manual — it's nilfs_sufile_truncate_range, and it's giving “truncate a range of the segment array” energy. 💅

🌸 NAME 🌸

nilfs_sufile_truncate_range — truncate range of segment array. 🎀

🦋 SYNOPSIS 🦋

       int nilfs_sufile_truncate_range (struct inode *sufile , __u64 start ,
       __u64 end );

💖 ARGUMENTS 💖

• sufile — inode of segment usage file. literally the inode for the segment usage file.
• start — start segment number (inclusive). yep, inclusive bestie.
• end — end segment number (inclusive). also inclusive, no sneaky off-by-one.

🔥 RETURN 🔥

0 on success, or one of the following negative error codes on failure:

• -EBUSY — Dirty or active segments are present in the range. so it's busy, not today.
• -EINVAL — Invalid number of segments specified. the segment count said “no ma'am.”
• -EIO — I/O error (including metadata corruption). 💀
• -ENOMEM — Insufficient memory available. out of memory, crying. 😭

🌈 SEE ALSO 🌈

• Kernel file ./fs/nilfs2/sufile.c
• struct nilfs_sufile_info(9)
• nilfs_sufile_segment_usage_offset(9)
• nilfs_sufile_get_ncleansegs(9)
• nilfs_sufile_updatev(9)
• nilfs_sufile_set_alloc_range(9)
• nilfs_sufile_alloc(9)
• nilfs_sufile_mark_dirty(9)
• nilfs_sufile_set_segment_usage(9)
• nilfs_sufile_get_stat(9)
• nilfs_sufile_resize(9)
• nilfs_sufile_get_suinfo(9)
• nilfs_sufile_set_suinfo(9)
• nilfs_sufile_trim_fs(9)
• nilfs_sufile_read(9)

mwah 💋 this page is from ./fs/nilfs2, dated October 2026, for nilfs_sufile_truncate_range(9) — slay and read the source, bestie. 🫶