Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
3
-
6037
Description
On ppc64, with lustre version 2.3.58-4chaos (which is 2.3.58, plus LLNL patches, plus a few that we've pulled in for testing), lfs setstripe no longer seems to work on ppc64 clients. I'm not sure at what point in time they stopped working.
Here's the error:
$ lfs setstripe -c 2 testfile error on ioctl 0x8008669a for 'testfile' (3): Invalid argument
Afterward there is a 0-length file created that has no stripe information, which makes sense if the striping ioctl() failed, but the mknod() succeeded.
I will attach the lustre log from running the above command. It is very verbose; I used "-1" debug level.
I believe that log was taken when running 2.3.58-5chaos. Looking at lov_getstripe, lov_packmd is called once, and obd_packmd is called once (which appears to then call lov_packmd).
Here's the source level information, with inlined git blame info for each line as well:
Looking at the git blame info, both calls have been in place for a long time. So this doesn't appear to be a discrepancy issue between our trees.. I'm curious why obd_free_diskmd (i.e. obd_packmd) isn't called in your local test case.