We are not sure if 1.5.97 really support failout mode, and if it doesn't, we should consider how to supprot this. We have noticed that if we set the failed OST deative both on client and mdt/mgs, it did what we want. We found the function ptlrpc_import_delay_req() in client.c, if we set the status to -EIO and delay to 0 when imp_state isn't LUSTRE_IMP_FULL, will it avoid blocking? and we also noticed imp->imp_obd->obd_no_recov, if set it to 1, will it avoid blocking? Or any body hava any good idea to solve this problem?
2007/3/22, swin wang <[EMAIL PROTECTED]>:
In our test, we didn't set the failout mode in mkfs, but set it on the mdt/mgs with lctl: lctl conf_param testfs-OST0001.failover.mode=failout but it seem didn't work. when OST0001 is failed, the client operation is still blocked (with 1.5.97). 2007/3/22, Nathaniel Rutman < [EMAIL PROTECTED]>: > > swin wang wrote: > > We current use 1.5.97, we try to set it to failout mode, but it didn't > > > work > > int this version, what we want is: when read/write the failed OST, > > it return > > IO errors, but still can create and read/write new files, when the > > failed OST > > is ok, we can read/write files on the failed OST. > That's what failout mode it. How did you try to set it? > > > I'm not sure if the 1.4.x version with "failout" mode can provide what > we > > want? > > >
_______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
