-
Notifications
You must be signed in to change notification settings - Fork 417
kernel hangs up while backend disk is missing #195
Comments
I have the same problem ,under Redhat 7 with kernel 3.10.0-123.el7.x86_64. |
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed. |
I have the same problem, I'm using flashcache 3.1.2, under RHEL 6.5 (kernel version: 2.6.32-431.el6.x86_64), format cachedev with xfs, WRITE_BACK mode <3>device-mapper: flashcache: flashcache_io_callback: io error -5 block 422251800 action 2 |
I have meet the same problem,I create a write back mode flashcache device, during I cp data to flashcache,I offline the SSD device, the flashcache happen panic, [1813726.692219] [] dump_stack+0x19/0x1b |
i have fix this issue, this commit will be ok if you need |
Hey guys,
I test flashcache under different kinds of exceptions, here is my step, I'm using flashcache 3.1.1 under centos 6.4 with kernel 3.10.58:
1 setup flashcache dev and format it with ext4;
2 write some data to the ext4;
3 unplug the the disk and writing some more data onto the cachedev, then there will be lots of error in syslog, then the kernel hangs up happendly;
in the src code, there is verify() function that will cause kernel panic, but in my testbed kernel hangup without any trace dump, only error report in flashcache_do_pending_error() like this:
kernel: device-mapper: flashcache: flashcache_do_pending_error: error -5 block 2360 action 2
kernel: device-mapper: flashcache: flashcache_io_callback: io error -5 block 6027584 action 2
so, pls give me some hints why the kernel hang up?
The text was updated successfully, but these errors were encountered: