Yes, I was using corruption to mean incomplete files. So, let me rephrase, is there a way to avoid "incomplete files" after an OSS crash, reboot, etc.? The lustre devices were not deactivated from the clients and MDS, would that possibly avoid the purge of data?
Thanks, Brian Stone Brian J. Murrell wrote: > On Wed, 2009-02-11 at 10:23 -0500, Brian Stone wrote: > >> My customer believes that this scenario is leading to corrupted files. >> > > What scenario? Recovery does not cause any corruption. At worst, > transactions from (some) clients will not get replayed and will be lost. > That's not generally what we consider "corruption" though. > > >> If so, is there any way to avoid the file corruption when an OSS goes down? >> > > Can you be more specific about what "corruption" you are seeing? > > Corruption by our definition is that on-disk, or on-the-wire data is > being altered by something other than a legitimate write from a client. > Corruption is not, for example, data simply not making it from the > client to disk. > > b. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss > _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
