It appears that this bug may not actually be related to bug #497326 as per the recent update in that thread. Perhaps this has more to do with the disk configuration that's being used?
It appears that this bug may not actually be related to bug #497326 as per the recent update in that thread. Perhaps this has more to do with the disk configuration that's being used?