“I am not able to specify -o to an existing file.”
Yes, that’s expected - As with any other setstripe command, you cannot apply it
to existing files which already have stripe information. (The exception is
files created with LOV_DELAY_CREATE or mknod(), which do not have striping
information
Responding to A. Dilger (orig e-mail copied below)
I am not sure what the overall objective is trying to achieve in
specifically identifying to which OSTs to write; it was a question from one
in our user community. I am not able to specify -o to an existing file.
I have not tried to use the
This is https://jira.whamcloud.com/browse/LU-8417 "setstripe -o does not work
on directories", which has not been implemented yet.
That said, setting the default striping to specific OSTs on a directory is
usually not the right thing to do. That will result in OST imbalance.
Equivalent
It looks like LU-10560 never got re-opened, even though the target was changed
to 2.10.6. I don’t see a patchset that Jenkins is happy about yet in Gerrit. Is
this still on track to land for 2.10.6?
Andrew Prout
Lincoln Laboratory Supercomputing Center
MIT Lincoln Laboratory
244 Wood
> On Nov 9, 2018, at 11:28 AM, Mohr Jr, Richard Frank (Rick Mohr)
> wrote:
>
>
>> On Nov 8, 2018, at 11:44 AM, Ms. Megan Larko wrote:
>>
>> I have been attempting this command on a directory on a Lustre-2.10.4
>> storage from a Lustre 2.10.1 client and I fail with the following message:
> On Nov 8, 2018, at 11:44 AM, Ms. Megan Larko wrote:
>
> I have been attempting this command on a directory on a Lustre-2.10.4 storage
> from a Lustre 2.10.1 client and I fail with the following message:
> > lfs setstripe -c 4 -S 1m -o 1,2-4 custTest/
> error on ioctl 0x4008669a for
All,
I asked this question a month or so back, but thought I'd ask it again to
see if anyone else had insight. I'm in the process of designing a new lustre
file system to replace an existing 2.3PB lustre file system. We have over a
thousand clients connecting to lustre over mostly QDR
