-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lvm2 writeback cache flush loops forever #22
Comments
A reboot of the node, forced the dirty blocks to not show up.
But if the whole vg is tried to be removed, then it results in strange errors as below now....
|
I installed now the thin-provisioning-tools package and cache_check is now made available.
|
On 7/30/19 6:45 AM, Lakshmi Narasimhan Sundararajan wrote:
I installed now the thin-provisioning-tools package and cache_check is now made available.
The dirty blocks for some reason did not show up earlier, now comes back again. The count suggests the IO is stuck.
```
***@***.***:~# apt-file search cache_check
thin-provisioning-tools: /usr/sbin/cache_check
thin-provisioning-tools: /usr/share/man/man8/cache_check.8.gz
***@***.***:~# apt-get install -y thin-provisioning-tools
Reading package lists... Done
...
Preparing to unpack .../thin-provisioning-tools_0.5.6-1ubuntu1_amd64.deb ...
Unpacking thin-provisioning-tools (0.5.6-1ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up thin-provisioning-tools (0.5.6-1ubuntu1) ...
***@***.***:~#
***@***.***:~#
***@***.***:~#
***@***.***:~# lvremove -f pwx0/pool
367 blocks must still be flushed.
367 blocks must still be flushed.
367 blocks must still be flushed.
367 blocks must still be flushed.
367 blocks must still be flushed.
367 blocks must still be flushed.
migration_threshold needs to be increased. See the following bug for
details:
https://bugzilla.redhat.com/show_bug.cgi?id=1668163#c3
Fixed in newer versions of LVM
…-- Martian
^C
***@***.***:~#
```
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lvmcache in writeback mode does not ever complete flush sometimes.
Can I please get some clarity on what exactly is the rootcause and when this was resolved?
Even putting the lvmcache into cleaner policy did not make any difference.
There is no kernel crash/traceback seen.
The text was updated successfully, but these errors were encountered: