MediaWiki API result
This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.
See the complete documentation, or the API help for more information.
{
"batchcomplete": "",
"continue": {
"lecontinue": "20260603230329|3068",
"continue": "-||"
},
"query": {
"logevents": [
{
"logid": 3078,
"ns": 0,
"title": "Mailing Lists and IRC",
"pageid": 1892,
"logpage": 283,
"params": {
"target_ns": 0,
"target_title": "Mailing Lists and Messaging"
},
"type": "move",
"action": "move",
"user": "Adilger",
"timestamp": "2026-07-23T22:26:11Z",
"comment": "Remove IRC from the title"
},
{
"logid": 3077,
"ns": 0,
"title": "Lustre Day to Day Operations",
"pageid": 1891,
"logpage": 1891,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-20T15:30:22Z",
"comment": "Created page with \"== Quick Reference == {| class=\"wikitable\" |- ! Task !! Command |- | Check filesystem health || <code>lctl get_param health_check</code> |- | List filesystem space || <code>lfs df -h</code> |- | List MDT/OST space || <code>lfs df -i</code> (inodes), <code>lfs df -h</code> (blocks) |- | Check server status || <code>lctl dl</code> |- | Mount a client || <code>mount -t lustre mgsnode@tcp:/fsname /mnt/fsname</code> |- | Unmount a client || <code>umount /mnt/fsname</code> |-...\""
},
{
"logid": 3076,
"ns": 0,
"title": "Lustre Rsync Replication",
"pageid": 1890,
"logpage": 1890,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-20T15:28:33Z",
"comment": "Created page with \"== Overview == <code>lustre_rsync</code> replicates a Lustre filesystem to another filesystem (Lustre or non-Lustre) using MDT changelogs. After an initial full sync, subsequent runs only process changes recorded since the last sync, making incremental replication efficient. == Prerequisites == * The source filesystem must have changelogs enabled on the MDT. * The target filesystem must be mounted and writable. * An initial full sync must be completed '''before''' reg...\""
},
{
"logid": 3075,
"ns": 0,
"title": "Lustre Backup Strategies",
"pageid": 1889,
"logpage": 1889,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-20T15:27:34Z",
"comment": "Created page with \"Lustre supports three primary backup strategies. Each serves different needs, and most production sites use a combination. {| class=\"wikitable\" |- ! Strategy !! Scope !! Speed !! Granularity !! Best For |- | File-level backup || Client-side || Slow for large FS || Individual files || Selective/incremental backups |- | Device-level backup || Per-target (MDT/OST) || Fast (streaming) || Entire device || Disaster recovery, hardware replacement |- | lustre_rsync || Changelog...\""
},
{
"logid": 3074,
"ns": 0,
"title": "Lustre Upgrade Checklist",
"pageid": 1888,
"logpage": 1888,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-20T15:25:37Z",
"comment": "Created page with \"== Purpose == This page is a '''condensed, actionable checklist''' for Lustre upgrades. It does '''not''' replace the full upgrade procedure \u2014 see [[Upgrading to a New Version of Lustre]] for the authoritative step-by-step guide. Use this page as a quick reference before, during, and after an upgrade. == Pre-Upgrade Preparation == Complete '''all''' of the following before beginning any upgrade: # '''Back up every MDT''' \u2014 <code>e2image -ra /dev/mdtdev /backup/md...\""
},
{
"logid": 3073,
"ns": 0,
"title": "Lustre Configuration Log Management",
"pageid": 1887,
"logpage": 1887,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-20T15:22:56Z",
"comment": "Created page with \"== Lustre Configuration Log Management == This page covers three powerful but '''potentially destructive''' commands for managing Lustre configuration logs: <code>writeconf</code>, <code>replace_nids</code>, and <code>clear_conf</code>. Understand the implications of each before using them. === Background === Lustre stores persistent configuration in '''configuration logs''' on the MGT. These logs tell servers and clients how to find each other and record persistent p...\""
},
{
"logid": 3072,
"ns": 0,
"title": "Lustre OST MDT Removal",
"pageid": 1886,
"logpage": 1886,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-06T15:33:41Z",
"comment": "Created page with \"== Lustre OST and MDT Removal == This page covers deactivating and removing OSTs and MDTs from a Lustre filesystem. These are '''high-stakes operations''' \u2014 read the warnings carefully before proceeding. For adding targets, see [[Lustre File System Expansion]]. === Removing an OST === There are three scenarios: migrating data off a working OST, handling a permanently failed OST, and temporary deactivation. ==== Scenario 1: Migrating Data Off a Working OST ==== Us...\""
},
{
"logid": 3071,
"ns": 0,
"title": "Lustre File System Expansion",
"pageid": 1885,
"logpage": 1885,
"params": {},
"type": "create",
"action": "create",
"user": "Elliswilson",
"timestamp": "2026-07-06T14:27:05Z",
"comment": "Created page with \"== Lustre File System Expansion: Adding MDTs and OSTs == This page provides step-by-step procedures for adding new OSTs and MDTs to an existing Lustre filesystem. These operations can be performed '''online''' \u2014 the filesystem remains available to clients during the expansion. For removing OSTs or MDTs, see [[Lustre OST MDT Removal]]. === Adding a New OST === Use this procedure to increase storage capacity. ==== Prerequisites ==== * A block device (or ZFS pool) f...\""
},
{
"logid": 3070,
"ns": 0,
"title": "Lustre User Group 2005",
"pageid": 1884,
"logpage": 1884,
"params": {},
"type": "create",
"action": "create",
"user": "Webmaster",
"timestamp": "2026-06-05T02:43:30Z",
"comment": "Created page with \"Cluster File Systems will host the third annual Lustre User Group meeting on March 7th and 8th in Snowbird, UT The Lustre User Group was founded by Pacific Northwest National Laboratory and Lawrence Livermore National Laboratory to promote the use of the open source Lustre file system for HPC and scalable IO. The annual meeting is an opportunity for current and prospective Lustre users to share and develop best practices, to provide direct feedback to the development t...\""
},
{
"logid": 3069,
"ns": 0,
"title": "Lustre User Group 2004",
"pageid": 1883,
"logpage": 1883,
"params": {},
"type": "create",
"action": "create",
"user": "Webmaster",
"timestamp": "2026-06-05T02:18:17Z",
"comment": "Created page with \" == 2004 Lustre User Group Meeting == Cluster File Systems, Inc. will host the second Lustre User Group Meeting in Maui, Hawaii on February 5th and 6th, 2004. The Lustre User Group was founded by Pacific Northwest National Laboratory and Lawrence Livermore National Laboratory to promote the use of the open source Lustre file system for HPC and scalable IO. We are working to develop a community knowledge base of best practices that make Lustre implementations successful...\""
}
]
}
}