I believe a 3.0 WiredTiger will set its major/minor to 3.0 even if compatible=(release=2.9) is passed in on the first wiredtiger_open call. This prevents WiredTiger 2.9 from opening the database, not because the data format is incompatible, but because of the version that's set.