Yes, that¹s to be expected. Lustre attempts to keep all OSTs equally full, so when you have a severe imbalance across OSTs, new files will preferentially be allocated on the empty OSTs.
One method for dealing with this is to have one node dedicated to rebalancing the data. It might take a long time, but it will get done eventually. -Ben Evans On 12/8/15, 12:41 PM, "lustre-discuss on behalf of John White" <[email protected] on behalf of [email protected]> wrote: >A month or two ago we expanded a lustre instance (added an OSS+OTSs to a >fairly full file system). Since then, we¹ve seen IO patterns that >heavily favor the new OSS/OSTs. In the default allocation strategy, is >this to be expected in a file system with heavily disparate free space >among OSTs? > >We don¹t really have the luxury of rebalancing things (assuming the >method for doing such is still ³re-write/copy files on old OSTs and let >the allocation strategy handle it"), unfortunately, so we¹re just looking >to confirm the behavior. >_______________________________________________ >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
