On Mon, 2013-07-08 at 19:56 +0300, Jarno Elonen wrote:
> Ok, I tried to take a photo but apparently the camera was set for very
> low resolution. :/ Anyway, a few pictures attached, and here's also a
> manual transcript of a few lines:
[...]
> [242866.xxxxxx] ata5.00: exception Emask 0x0 SAct 0x0 SError 0x0
> action 0x6 frozen
> [242866.xxxxxx] ata5.00: failed command: FLUSH CACHE EXT
> [242866.xxxxxx] ata8.00: exception Emask 0x0 SAct 0x0 SError 0x0
> action 0x6 frozen
> [242866.xxxxxx] ata8.00: failed command: FLUSH CACHE EXT
> [242866.xxxxxx] ata8.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [242866.xxxxxx] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask
> 0x4 (timeout)
> [242866.xxxxxx] ata8.00: status { DRDY }
> [242867.xxxxxx] ata5.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> ...
> [242877.xxxxxx] ata3: COMRESET failed (errno=-16)
> [242877.xxxxxx] ata5: COMRESET failed (errno=-16)
> ...
>
> These kinds of splurs com up once in a minute or so.
This suggests to me that LVM is *not* part of the problem, but instead
the disks are being shut down before bcache has been quiesced.
bcache developers - is this supposed to just work, or does the init
system need to do (or not do) something special for bcache devices?
Ben.
--
Ben Hutchings
It is easier to write an incorrect program than to understand a correct one.
Attachment:
signature.asc
Description: This is a digitally signed message part