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.
I'm not sure if the 1.4.x version with "failout" mode can provide what we
want?
2007/3/21, Andreas Dilger <[EMAIL PROTECTED]>:
On Mar 21, 2007 10:29 +0800, swin wang wrote:
> I know this configuration, but I hope it can automatically bypass the
> failed OST, because I can't make sure when the OST will be failed, mybe
> my question is how to avoid blocking rpc on OST, but instead of return
> IO error, whenever the OST is failed.
If you prefer getting IO errors to your application instead of waiting
for recovery, then you can configure the OST with "failout" using the
--failout option in 1.4. Lustre clients will never retry failed RPCs
in this mode.
> 2007/3/21, Andreas Dilger <[EMAIL PROTECTED]>:
>
> On the clients run:
> >
> >lctl dl # list lustre device configuration
> >lctl --device {failed OST device number} deactivate
> >
> >Same on the MDS, though the device will be different compared to
clients.
> >
> >This will deactivate the failed OST on the clients so they get an IO
error
> >when accessing any files on the OST, instead of waiting for it to
recover.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
