[Lustre-discuss] Performance dropoff for a nearly full Lustre file system

[Mike Selway]

Hello,
               I'm looking for experiences for what has been observed to happen (performance drop offs, severity of drops, partial/full failures, ...) when an operational Lustre File System has been almost "filled"... percentages of interest are in the range from say 80% to 99%.  Multiple responses appreciated.

Also, comments from anyone who has implemented a Robin Hood approach, about how they worked to avoid performance drop offs of a "near full" file system by "archiving and releasing data blocks" to auto-reconstruct continuous data areas.

Thanks!
Mike

Mike Selway | Sr. Storage Architect (TAS) | Cray Inc.
Work +1-301-332-4116 | mselway at cray.com
146 Castlemaine Ct,   Castle Rock,  CO  80104|   Check out Tiered Adaptive Storage (TAS)!<http://www.cray.com/Products/Storage/Tiered-Adaptive-Storage.aspx>

[cid:image001.png at 01CF36E5.85AF42A0]<http://www.cray.com/>
[cid:image002.jpg at 01D02FF7.A1B0F1E0]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20150114/65e3298d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5290 bytes
Desc: image001.png
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20150114/65e3298d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2329 bytes
Desc: image002.jpg
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20150114/65e3298d/attachment.jpg>