[Lustre-devel] async write and abort_recov

Aurelien Degremont aurelien.degremont at cea.fr
Mon Jul 12 03:10:04 PDT 2010


I'm wondering how Lustre client handles recovery when OST restarts with abort_recov flag set.

Let's say a client has page to flush to OST, but OST is stopped, then restarts with -o abort_recov.
There is no recovery, so:
1- client retakes extent locks and then re-try to flush its pages
2- client cannot flush anymore and drop the i/o, returns an error to the caller.

If #2, what if the process has already closed the file ?
What is the file is still opened and the process try to do another I/O, will it have an error for the former bad i/o?

abort_recov is used only at first start, or the OST uses this flag until it is stopped for any other recovery-like


Aurelien Degremont

More information about the lustre-devel mailing list