[Lustre-devel] Wide striping

Andreas Dilger adilger at whamcloud.com
Wed Oct 5 18:51:37 PDT 2011

On 2011-10-05, at 9:33 AM, David Dillow <dillowda at ornl.gov> wrote:
> On Wed, 2011-10-05 at 11:06 -0400, Nathan Rutman wrote:
>> Sorry if I'm being unclear.
>> start_index is just an offset into the bitmap.  That's the OST where the first 
>> stripe will be.  Next stripe will be on the next OST index (unless a hole). 
>> When we get to the big hole at the end of the used OSTs, these OST index 
>> locations are all skipped (since they are holes), and the next stripe will 
>> be at OST index 0, then 1, etc, up to start_index-1 (again, unless holes).
> Ok, so bitmap position 0 is always OST 0; thanks for clearing up my
> misunderstanding.

But this means that the table always needs to be as large as the maximum OST number. If the bitmap started at the starting OST index it would only need to be as large as the number of stripes. 

That said, the limitation if not being able to migrate objects with this layout is a major one. The ability to so online object migration is just arriving with the layout lock (from HSM), so I expect this to be useful to many users. 

Cheers, Andreas

More information about the lustre-devel mailing list