Hi, I am the developer of DM-Writeboost. I am not sure what the problem is. Is the problem caching driver may update the underlying devices before resume? If so, stopping daemons will do by sending the driver these messages - allow_writeback 0 - enable_writeback_modulator 0 - update_record_interval 0 The first two stops writeback and the third one stops periodical update of the superblock sector. btw, DM-Writeboost isn't in LVM family yet so this problem won't happen at the moment however, I doesn't mean I can be unaware. Thanks. - Akira -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
