It can be pretty easily inferred from the nature of the feature.
If a decent policy is written and applied to all files (starting with few stripes and going to many as size increases), then it will resolve the problem of large files on single OSTs. If the policy is not universally applied or is poorly constructed, you may have issues. Otherwise, as long as users are not restricting file creation to a single or small # of OSTs, then there's not really any way for them to fill up a single OST without filling up all of them. - Patrick ________________________________ From: lustre-discuss <[email protected]> on behalf of Mark Hahn <[email protected]> Sent: Tuesday, October 24, 2017 3:21:47 PM To: Lustre Discuss Subject: Re: [lustre-discuss] ZFS-OST layout, number of OSTs > It?s also worth noting that if you have small OSTs it?s much easier to bump >into a full OST situation. And specifically, if you singly stripe a file >the file size is limited by the size of the OST. is there enough real-life experience to know whether progressive file layout will mitigate this issue? thanks, Mark Hahn | SHARCnet Sysadmin | [email protected] | http://www.sharcnet.ca | McMaster RHPCS | [email protected] | 905 525 9140 x24687 | Compute/Calcul Canada | http://www.computecanada.ca _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
_______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
