From: vaLentin chernoZemski <valentin@siteground.com>
To: dm-devel@redhat.com
Cc: SiteGround Operations <operations@siteground.com>
Subject: lvremove kernel BUG at drivers/md/dm-bufio.c:1494!
Date: Thu, 19 Nov 2015 17:14:08 +0200 [thread overview]
Message-ID: <564DE740.3040104@siteground.com> (raw)
Hi folks,
It seems that there is a bug in the linux kernel in any release from
- 2.6.32-573.3.1.el6.x86_64 - crash
- 3.12.49 + msg00123 patch - crash / D state
- 4.1.6 - lv* operations in D state after bug is hit
- 4.1.12 + f11a82caf / b0dc3c8bc15 - lv* operations in D state after
bug is hit
- 4.2.5 - lv* operations in D state after bug is hit
- 4.3.0-rc7-vanilla1
The bug is described in details and stack traces in RedHat's bugzilla
under id 1219634:
https://bugzilla.redhat.com/show_bug.cgi?id=1219634
For some reason it is marked as private but I guess you have access to
this one.
Issue is present in current latest RHEL version and all vanilla kernels
I tested with multiple patches specified in the bug.
Even I can not provide you with exact reproducer it happens often enough
on a fleet of machines we have that perform certain tasks and we can
easily test new patches or provide you with specific information upon
request from all crash dumps we reliably collected and still collecting
from all kernel versions tested.
I got advised by Mike Snitzer to dm-devel so here it is.
Let us know if there is anything we can do to assist you further.
Regards,
vaLenitn
next reply other threads:[~2015-11-19 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 15:14 vaLentin chernoZemski [this message]
2015-11-20 19:46 ` lvremove kernel BUG at drivers/md/dm-bufio.c:1494! Mike Snitzer
2015-11-20 21:41 ` Marian Marinov
2015-12-12 9:21 ` Nikolay Borisov
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=564DE740.3040104@siteground.com \
--to=valentin@siteground.com \
--cc=dm-devel@redhat.com \
--cc=operations@siteground.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.