Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=11519
the code in llapi_lov_get_uuids computes max_ost_count based on things that
don't change:
max_ost_count = (OBD_MAX_IOCTL_BUFFER - size_round(sizeof(data)) -
size_round(sizeof(desc))) /
(sizeof(*uuidp) + sizeof(*obdgens));
It's 171 all the time here. Then it's used to calculate how much uuid buffer to
use, and to fill in data.ioc_inllen2 with a value which is definitely going to
be less than the actual ost count times the sizeof the uuid entry. We'll confirm
that monday.
I'm thinking a build with a config option raising the size of
OBD_MAX_IOCTL_BUFFER might solve the lfsck problem. I'm not sure of other
effects of that change though. Besides lov.ko, and lfsck what other
modules/utilities might have to be swapped? Or is there a reason this won't work
at all?
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
