From: Akira Hayakawa <ruby.wktk@gmail.com>
To: dm-devel@redhat.com
Cc: kmo@daterainc.com, mathijs@bluescreen303.nl
Subject: Re: Hibernate/Resume and dm-cache, dm-writeboost...
Date: Tue, 30 Dec 2014 20:34:23 +0900 [thread overview]
Message-ID: <54A28DBF.9060909@gmail.com> (raw)
In-Reply-To: <20141230103228.GA31888@debian>
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
prev parent reply other threads:[~2014-12-30 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 18:35 Hibernate/Resume and dm-cache, dm-writeboost Rolf Fokkens
2014-12-30 10:32 ` Joe Thornber
2014-12-30 11:34 ` Akira Hayakawa [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54A28DBF.9060909@gmail.com \
--to=ruby.wktk@gmail.com \
--cc=dm-devel@redhat.com \
--cc=kmo@daterainc.com \
--cc=mathijs@bluescreen303.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox