Lustre 1.6 Operations Manual

22. Lustre Troubleshooting Tips 22–1
22.1 Troubleshooting Lustre 22–1
22.1.1 Lustre Error Messages 22–1
22.1.2 Lustre Logs 22–2
22.2 Submitting a Lustre Bug 22–3
22.3 Lustre Performance Tips 22–4
22.3.1 Setting SCSI I/O Sizes 22–4
22.3.2 Write Performance Better Than Read Performance 22–4
22.3.3 OST Object is Missing or Damaged 22–5
22.3.4 OSTs Become Read-Only 22–6
22.3.5 Identifying a Missing OST 22–6
22.3.6 Changing Parameters 22–8
22.3.7 Viewing Parameters 22–9
22.3.8 Default Striping 22–10
22.3.9 Erasing a Filesystem 22–10
22.3.10 Reclaiming Reserved Disk Space 22–11
22.3.11 Considerations in Connecting a SAN with Lustre 22–11
22.3.12 Handling/Debugging "Bind: Address already in use" Error 22–12
22.3.13 Replacing An Existing OST or MDS 22–13
22.3.14 Handling/Debugging Error "- 28" 22–13
22.3.15 Triggering Watchdog for PID NNN 22–14
22.3.16 Handling Timeouts on Initial Lustre Setup 22–15
22.3.17 Handling/Debugging "LustreError: xxx went back in time" 22–16
22.3.18 Lustre Error: "Slow Start_Page_Write" 22–16
22.3.19 Drawbacks in Doing Multi-client O_APPEND Writes 22–17
22.3.20 Slowdown Occurs During Lustre Startup 22–17
22.3.21 Log Message ‘Out of Memory’ on OST 22–17
22.3.22 Number of OSTs Needed for Sustained Throughput 22–18
xvi Lustre 1.6 Operations Manual • September 2008