Is the read cache corruption actually causing on-disk corruption? Or just in-memory corruption? I'm assuming the write cache corruption would end up causing the file to become corrupt on disk, but if a node crashes during a write then I'm personally not all that bothered by it.
On a side note, any advice about how to avoid buggy releases or how to select a stable older release would be much appreciated. Also, is 1.8 considered "stable" and/or "production-ready", or should I be using the 1.6 series currently? Thanks! On Wed, Sep 9, 2009 at 11:00 AM, Johann Lombardi <[email protected]> wrote: > A bug has been identified in the 1.8 releases (1.8.0, 1.8.0.1 & 1.8.1 > are > impacted) that can cause data corruption on the OSTs. This problem is > related to the OSS read cache feature that has been introduced in 1.8.0. > This can happen when a bulk read or write request is aborted due to the > client being evicted or because the data transfer over the network has > timed out. More details are available in bug 20560: > https://bugzilla.lustre.org/show_bug.cgi?id=20560 > > A patch is under testing and will be included in 1.8.1.1. > Until 1.8.1.1 is available, we recommend to disable the OSS read cache > feature. This feature can be disabled by running the two following > commands on the OSSs: > # lctl set_param obdfilter.*.writethrough_cache_enable=0 > # lctl set_param obdfilter.*.read_cache_enable=0 > > This has to be done each time an OST is restarted. > > Best regards, > Johann, for the Lustre team > _______________________________________________ > 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
