Created
March 16, 2018 03:43
-
-
Save nugielim/e2ccbcac555fcd87123d9b6c66e1b383 to your computer and use it in GitHub Desktop.
nvme error gcp
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mar 16 02:39:27 allocator-uw1-allocator-v1-a-714m kernel: [ 162.071677] aufs au_opts_verify:1597:docker[2571]: dirperm1 breaks the protection by the permission bits on the lower branch | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.496660] nvme 0000:00:04.0: I/O 111 QID 8 timeout, aborting | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.497121] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.720667] nvme 0000:00:04.0: I/O 631 QID 8 timeout, aborting | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.720880] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.736671] nvme 0000:00:04.0: I/O 902 QID 8 timeout, aborting | |
Mar 16 02:39:44 allocator-uw1-allocator-v1-a-714m kernel: [ 178.736793] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.496676] nvme 0000:00:04.0: I/O 68 QID 8 timeout, aborting | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.497084] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.720663] nvme 0000:00:04.0: I/O 578 QID 8 timeout, aborting | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.720877] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.728645] nvme 0000:00:04.0: I/O 84 QID 8 timeout, aborting | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.728756] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.736659] nvme 0000:00:04.0: I/O 903 QID 8 timeout, aborting | |
Mar 16 02:39:48 allocator-uw1-allocator-v1-a-714m kernel: [ 182.736761] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.488688] nvme 0000:00:04.0: I/O [ 209.500291] blk_update_request: I/O error, dev nvme0n7, sector 0 | |
[ 209.507520] blk_update_request: I/O error, dev nvme0n6, sector 0 | |
[ 209.513630] blk_update_request: I/O error, dev nvme0n5, sector 0 | |
[ 209.519739] blk_update_request: I/O error, dev nvme0n4, sector 0 | |
[ 209.525858] blk_update_request: I/O error, dev nvme0n3, sector 0 | |
[ 209.531971] blk_update_request: I/O error, dev nvme0n1, sector 0 | |
[ 209.538080] blk_update_request: I/O error, dev nvme0n6, sector 714440656 | |
[ 209.544896] blk_update_request: I/O error, dev nvme0n6, sector 714440664 | |
[ 209.551708] blk_update_request: I/O error, dev nvme0n6, sector 714440672 | |
[ 209.558517] blk_update_request: I/O error, dev nvme0n6, sector 714440680 | |
111 QID 8 timeou[ 209.567049] Buffer I/O error on dev dm-1, logical block 696124794, lost async page write | |
t, reset control[ 209.576635] Buffer I/O error on dev dm-1, logical block 696124795, lost async page write | |
ler | |
Mar 16 02:4[ 209.586208] Buffer I/O error on dev dm-1, logical block 696124796, lost async page write | |
0:15 allocator-u[ 209.595783] Buffer I/O error on dev dm-1, logical block 696124797, lost async page write | |
w1-allocator-v1-[ 209.605377] Buffer I/O error on dev dm-1, logical block 696124798, lost async page write | |
a-714m kernel: [[ 209.614961] Buffer I/O error on dev dm-1, logical block 696124799, lost async page write | |
209.500286] nv[ 209.624555] Buffer I/O error on dev dm-1, logical block 696124988, lost async page write | |
me 0000:00:04.0:[ 209.634139] Buffer I/O error on dev dm-1, logical block 696124989, lost async page write | |
completing abor[ 209.643747] Buffer I/O error on dev dm-1, logical block 696124990, lost async page write | |
ted command with[ 209.653331] Buffer I/O error on dev dm-1, logical block 696125010, lost async page write | |
status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.500291] blk_update_request: I/O error, dev nvme0n7, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.507517] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.507520] blk_update_request: I/O error, dev nvme0n6, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.513628] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.513630] blk_update_request: I/O error, dev nvme0n5, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.519737] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.519739] blk_update_request: I/O error, dev nvme0n4, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.525855] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.525858] blk_update_request: I/O error, dev nvme0n3, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.531969] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.531971] blk_update_request: I/O error, dev nvme0n1, sector 0 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.538079] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.538080] blk_update_request: I/O error, dev nvme0n6, sector 714440656 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.544894] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.544896] blk_update_request: I/O error, dev nvme0n6, sector 714440664 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.551707] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.551708] blk_update_request: I/O error, dev nvme0n6, sector 714440672 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.558515] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.558517] blk_update_request: I/O error, dev nvme0n6, sector 714440680 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565326] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565329] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565332] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565335] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565337] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565339] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565347] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565350] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565352] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565355] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565357] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565359] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565362] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565364] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565366] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565369] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565372] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565375] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565377] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565381] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565384] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565387] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565389] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565393] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565397] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565400] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565403] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565405] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565407] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565410] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565412] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565415] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565417] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565419] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565422] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565424] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565426] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565428] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565431] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565434] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565436] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565438] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565441] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565443] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565445] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565447] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565449] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565453] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565456] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565458] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565460] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565463] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565465] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565467] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565470] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565473] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565475] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565478] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565480] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565482] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565484] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565487] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565490] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565493] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565496] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565498] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565501] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565503] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565506] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565509] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565511] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565513] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565517] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565521] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565523] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565526] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565529] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565532] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565535] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565537] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565539] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565543] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565545] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565547] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565549] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565552] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565554] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565556] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565559] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565563] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565574] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565578] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565582] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565586] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565589] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565591] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565595] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565598] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565601] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565604] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565607] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565611] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565613] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565615] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565618] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565622] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565625] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565627] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565630] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565633] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565635] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565638] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565641] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565644] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565646] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565649] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565652] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565654] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565657] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565660] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565664] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565666] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565669] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565672] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565676] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565679] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565681] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565683] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565687] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565690] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565693] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565696] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565699] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565702] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565706] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565708] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565712] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565715] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565718] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565721] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565724] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565727] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565730] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565732] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565735] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565738] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565741] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565744] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565747] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565750] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565753] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565755] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565758] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565762] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565764] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565767] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565770] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565773] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565775] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565777] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565780] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565782] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565784] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565787] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565789] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565791] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565794] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565796] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565799] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565801] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565803] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565805] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565808] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565810] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565813] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565815] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565818] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565820] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565822] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565824] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565826] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565828] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565830] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565833] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565835] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565837] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565839] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565842] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565844] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565846] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565848] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565850] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565853] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565855] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565858] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565861] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565863] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565865] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565868] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565871] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565874] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565876] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565879] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565881] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565883] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565885] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565888] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565891] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565894] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565896] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565899] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565902] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565904] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565906] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565909] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565912] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565915] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565918] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565921] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565924] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565926] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565929] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565931] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565933] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565935] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565938] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565941] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565944] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565946] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565949] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565951] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565955] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565957] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565960] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565962] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565964] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565967] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565970] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565972] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565974] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565976] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565978] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565981] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565983] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565986] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565989] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565991] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565994] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565996] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.565998] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566000] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566003] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566005] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566007] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566009] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566011] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566013] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566016] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566018] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566020] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566023] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566025] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566027] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566029] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566031] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566033] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566035] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566038] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566040] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566043] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566045] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566048] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566050] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566052] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566055] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566057] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566060] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566062] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566064] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566067] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566069] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566071] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566073] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566075] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566077] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566080] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566082] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566084] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566086] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566089] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566091] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566093] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566096] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566098] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566099] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566101] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566103] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566106] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566108] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566111] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566113] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566115] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566117] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566119] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566121] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566125] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566127] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566129] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566131] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566134] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566136] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566138] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566140] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566142] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566145] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566147] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566149] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566152] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566155] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566157] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566159] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566162] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566165] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566167] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566168] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566171] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566173] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566175] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566177] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566179] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566181] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566184] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566187] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566189] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566191] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566193] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566195] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566197] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566200] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566202] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566203] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566206] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566208] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566210] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566212] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566215] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566216] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566219] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566221] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566223] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566226] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566228] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566230] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566232] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566234] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566236] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566238] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566241] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566243] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566246] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566248] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566250] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566253] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566255] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566257] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566259] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566261] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566263] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566266] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566269] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566272] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566274] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566276] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566279] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566281] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566282] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566284] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566286] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566288] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566291] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566292] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566295] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566297] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566299] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566302] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566304] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566307] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566309] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566311] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566314] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566316] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566318] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566321] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566324] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566326] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566329] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566331] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566333] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566336] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566338] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566341] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566343] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566345] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566348] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566350] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566352] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566354] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566356] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566359] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566362] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566365] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566367] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566369] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566372] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566374] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566376] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566378] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566381] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566383] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566386] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566388] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566390] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566393] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566395] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566398] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566400] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566402] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566405] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566407] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566410] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566412] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566414] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566416] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566418] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566421] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566423] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566425] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566428] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566430] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566432] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566434] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566437] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566439] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566441] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566443] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566445] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566447] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566450] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566452] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566454] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566456] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566458] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566460] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566463] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566465] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566468] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566470] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566473] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566476] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566478] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566480] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566483] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566485] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566488] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566490] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566493] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566495] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566498] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566500] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566502] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566504] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566507] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566510] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566512] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566514] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566516] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566518] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566521] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566522] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566526] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566528] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566531] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566533] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566535] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566537] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566540] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566542] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566544] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566547] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566549] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566551] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566553] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566555] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566558] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566561] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566563] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566566] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566572] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566575] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566577] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566579] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566581] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566585] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566587] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566590] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566592] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566594] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566597] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566599] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566601] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566604] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566606] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566608] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566610] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566613] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566616] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566618] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566620] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566622] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566624] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566626] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566629] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566631] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566633] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566635] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566638] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566640] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566642] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566645] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566647] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566649] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566652] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566655] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566658] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566660] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566663] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566665] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566667] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566669] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566671] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566674] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566676] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566678] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566680] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566684] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566686] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566689] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566691] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566694] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566696] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566698] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566700] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566702] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566705] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566706] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566708] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566710] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566712] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566714] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566716] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566718] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566720] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566722] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566725] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566727] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566730] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566732] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566734] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566737] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566740] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566742] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566745] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566747] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566749] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566751] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566754] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566756] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566758] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566760] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566762] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566764] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566767] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566769] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566772] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566774] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566776] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566778] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566781] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566783] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566785] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566787] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566790] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566792] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566794] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566796] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566799] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566802] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566804] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566808] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566810] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566812] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566814] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566817] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566819] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566821] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566824] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566826] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566827] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566830] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566832] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566834] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566837] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566838] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566841] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566844] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566846] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566849] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566851] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566854] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566857] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566860] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566862] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566864] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566866] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566868] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.566870] nvme 0000:00:04.0: completing aborted command with status: 0008 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.567049] Buffer I/O error on dev dm-1, logical block 696124794, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.576635] Buffer I/O error on dev dm-1, logical block 696124795, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.586208] Buffer I/O error on dev dm-1, logical block 696124796, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.595783] Buffer I/O error on dev dm-1, logical block 696124797, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.605377] Buffer I/O error on dev dm-1, logical block 696124798, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.614961] Buffer I/O error on dev dm-1, logical block 696124799, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.624555] Buffer I/O error on dev dm-1, logical block 696124988, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.634139] Buffer I/O error on dev dm-1, logical block 696124989, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.643747] Buffer I/O error on dev dm-1, logical block 696124990, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.653331] Buffer I/O error on dev dm-1, logical block 696125010, lost async page write | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.696534] nvme 0000:00:04.0: Cancelling I/O 111 QID 8 | |
Mar 16 02:40:15 allocator-uw1-allocator-v1-a-714m kernel: [ 209.696574] nvme 0000:00:04.0: completing aborted command with status: fffffffc | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570460] audit_printk_skb: 27 callbacks suppressed | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570463] audit: type=1400 audit(1521168016.137:39): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570563] audit: type=1400 audit(1521168016.137:40): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570582] audit: type=1400 audit(1521168016.137:41): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570733] audit: type=1400 audit(1521168016.137:42): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570835] audit: type=1400 audit(1521168016.137:43): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:16 allocator-uw1-allocator-v1-a-714m kernel: [ 210.570854] audit: type=1400 audit(1521168016.137:44): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14931 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:17 allocator-uw1-allocator-v1-a-714m kernel: [ 212.223040] audit: type=1400 audit(1521168017.789:45): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=20633 comm="cat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:17 allocator-uw1-allocator-v1-a-714m kernel: [ 212.227819] audit: type=1400 audit(1521168017.793:46): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=20639 comm="cat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.488682] nvme 0000:00:04.0: I/O 657 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.489128] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.544672] nvme 0000:00:04.0: I/O 346 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.544802] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.604674] nvme 0000:00:04.0: I/O 546 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.604810] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.676665] nvme 0000:00:04.0: I/O 142 QID 2 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.676895] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.716652] nvme 0000:00:04.0: I/O 896 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.716774] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.736655] nvme 0000:00:04.0: I/O 810 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.736773] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.740651] nvme 0000:00:04.0: I/O 904 QID 1 timeout, aborting | |
Mar 16 02:40:46 allocator-uw1-allocator-v1-a-714m kernel: [ 240.740735] nvme 0000:00:04.0: Abort status:0 result:1 | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.496674] nvme 0000:00:04.0: I/O 657 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.560650] nvme 0000:00:04.0: I/O 346 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.571906] audit: type=1400 audit(1521168076.137:47): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.572015] audit: type=1400 audit(1521168076.137:48): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.572037] audit: type=1400 audit(1521168076.137:49): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.572188] audit: type=1400 audit(1521168076.137:50): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.572303] audit: type=1400 audit(1521168076.137:51): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.572323] audit: type=1400 audit(1521168076.137:52): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.624655] nvme 0000:00:04.0: I/O 546 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.624662] nvme 0000:00:04.0: I/O 0 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.688662] nvme 0000:00:04.0: I/O 142 QID 2 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.720657] nvme 0000:00:04.0: I/O 896 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.736662] nvme 0000:00:04.0: I/O 810 QID 1 timeout, reset controller | |
Mar 16 02:41:16 allocator-uw1-allocator-v1-a-714m kernel: [ 270.752656] nvme 0000:00:04.0: I/O 904 QID 1 timeout, reset controller | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.570787] audit: type=1400 audit(1521168136.137:53): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.570886] audit: type=1400 audit(1521168136.137:54): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.570904] audit: type=1400 audit(1521168136.137:55): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.571066] audit: type=1400 audit(1521168136.137:56): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.571168] audit: type=1400 audit(1521168136.137:57): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:16 allocator-uw1-allocator-v1-a-714m kernel: [ 330.571188] audit: type=1400 audit(1521168136.137:58): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14957 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:42:43 allocator-uw1-allocator-v1-a-714m ntpd[2012]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized | |
[ 362.334859] INFO: task kworker/u44:2:249 blocked for more than 120 seconds. | |
[ 362.341971] Not tainted 4.4.0-109-generic #132-Ubuntu | |
[ 362.347663] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:47 [ 362.355693] INFO: task kworker/5:1H:762 blocked for more than 120 seconds. | |
[ 362.364048] Not tainted 4.4.0-109-generic #132-Ubuntu | |
allocator-uw1-al[ 362.369732] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
locator-v1-a-714[ 362.379203] INFO: task kworker/5:2:1137 blocked for more than 120 seconds. | |
m kernel: [ 362[ 362.387419] Not tainted 4.4.0-109-generic #132-Ubuntu | |
.334859] INFO: t[ 362.394491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
ask kworker/u44:[ 362.404045] INFO: task docker:2571 blocked for more than 120 seconds. | |
2:249 blocked fo[ 362.411764] Not tainted 4.4.0-109-generic #132-Ubuntu | |
r more than 120 [ 362.418839] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
seconds. | |
Mar 16[ 362.428419] INFO: task filebeat:14831 blocked for more than 120 seconds. | |
[ 362.436389] Not tainted 4.4.0-109-generic #132-Ubuntu | |
02:42:47 alloca[ 362.442075] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
tor-uw1-allocator-v1-a-714m kernel: [ 362.341971] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.347663] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355602] kworker/u44:2 D ffff8800360d7be8 0 249 2 0x00000000 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355610] Workqueue: nvme nvme_dev_scan [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355612] ffff8800360d7be8 0000000000000000 ffffffff81e13500 ffff882292526200 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355618] ffff8800360d8000 ffff8822917ab8e0 0000000000000000 0000000000001000 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355622] ffff882292b3dd00 ffff8800360d7c00 ffffffff818404e5 ffff8822917ab430 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355624] Call Trace: | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355630] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355634] [<ffffffff813d5767>] blk_mq_freeze_queue_wait+0x57/0xc0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355641] [<ffffffff810c4eb0>] ? wake_atomic_t_function+0x60/0x60 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355644] [<ffffffff813d71da>] blk_mq_freeze_queue+0x1a/0x20 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355648] [<ffffffffc0025644>] nvme_revalidate_disk+0x144/0x460 [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355652] [<ffffffff8124dab8>] revalidate_disk+0x28/0x80 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355656] [<ffffffffc00259a5>] nvme_validate_ns+0x45/0x240 [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355660] [<ffffffffc00262a1>] nvme_scan_namespaces+0xc1/0x330 [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355663] [<ffffffff810ab6e5>] ? resched_curr+0x65/0xc0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355666] [<ffffffffc0027c1f>] ? nvme_async_event_work+0x7f/0xc0 [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355668] [<ffffffffc0027277>] nvme_dev_scan+0x27/0x80 [nvme] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355672] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355674] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355676] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355678] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355679] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355684] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355685] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.355693] INFO: task kworker/5:1H:762 blocked for more than 120 seconds. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.364048] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.369732] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379049] kworker/5:1H D ffff882290c67b18 0 762 2 0x00000000 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379084] Workqueue: xfs-log/dm-1 xfs_log_worker [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379086] ffff882290c67b18 00000021eb016745 ffff882299dd7000 ffff882290764600 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379088] ffff882290c68000 ffff882290c67c78 ffff882290c67c70 ffff882290764600 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379098] ffffffffffffffff ffff882290c67b30 ffffffff818404e5 7fffffffffffffff | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379100] Call Trace: | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379102] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379104] [<ffffffff81843635>] schedule_timeout+0x1b5/0x270 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379106] [<ffffffff810ac1f0>] ? check_preempt_curr+0x80/0x90 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379108] [<ffffffff810ac219>] ? ttwu_do_wakeup+0x19/0xe0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379109] [<ffffffff810acdc9>] ? try_to_wake_up+0x49/0x3f0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379111] [<ffffffff81840f43>] wait_for_completion+0xb3/0x140 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379113] [<ffffffff810ad200>] ? wake_up_q+0x70/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379115] [<ffffffff8109c17d>] flush_work+0x10d/0x1c0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379116] [<ffffffff81098340>] ? destroy_worker+0x90/0x90 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379133] [<ffffffffc04a01bb>] xlog_cil_force_lsn+0x8b/0x210 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379135] [<ffffffff81099359>] ? __queue_work+0x139/0x3c0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379138] [<ffffffff810ba5b5>] ? put_prev_entity+0x35/0x7d0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379153] [<ffffffffc049e355>] _xfs_log_force+0x85/0x2a0 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379157] [<ffffffff8102d66c>] ? __switch_to+0x1dc/0x5c0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379172] [<ffffffffc049e596>] xfs_log_force+0x26/0x90 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379186] [<ffffffffc049e624>] xfs_log_worker+0x24/0x50 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379188] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379190] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379192] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379193] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379195] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379198] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379199] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.379203] INFO: task kworker/5:2:1137 blocked for more than 120 seconds. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.387419] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.394491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403820] kworker/5:2 D ffff882297287958 0 1137 2 0x00000000 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403841] Workqueue: xfs-cil/dm-1 xlog_cil_push_work [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403844] ffff882297287958 dead000000000200 ffff882293acaa00 ffff88228f4cc600 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403846] ffff882297288000 ffff8822902d5290 ffff8822902d5298 ffff881f591fdf20 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403847] 0000000000000000 ffff882297287970 ffffffff818404e5 ffff8822902d5000 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403852] Call Trace: | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403854] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403859] [<ffffffff816b0558>] md_flush_request+0x78/0x130 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403862] [<ffffffff810c4eb0>] ? wake_atomic_t_function+0x60/0x60 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403865] [<ffffffffc000839d>] raid0_make_request+0x21d/0x230 [raid0] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403867] [<ffffffff816ab830>] md_make_request+0x100/0x230 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403869] [<ffffffff816be304>] ? dm_make_request+0x74/0xc0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403871] [<ffffffff813cb9ff>] generic_make_request+0x10f/0x2c0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403874] [<ffffffff813c325e>] ? bvec_alloc+0x5e/0x100 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403875] [<ffffffff813cbc26>] submit_bio+0x76/0x170 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403891] [<ffffffffc047a69e>] _xfs_buf_ioapply+0x2de/0x490 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403908] [<ffffffffc049b5cb>] ? xlog_bdstrat+0x2b/0x60 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403924] [<ffffffffc047be74>] xfs_buf_submit+0x64/0x1c0 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403942] [<ffffffffc049b5cb>] xlog_bdstrat+0x2b/0x60 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403957] [<ffffffffc049d475>] xlog_sync+0x2d5/0x400 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403971] [<ffffffffc049d616>] xlog_state_release_iclog+0x76/0xc0 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403984] [<ffffffffc049e0b2>] xlog_write+0x5d2/0x700 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.403998] [<ffffffffc049f93b>] xlog_cil_push+0x22b/0x3f0 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404012] [<ffffffffc049fb15>] xlog_cil_push_work+0x15/0x20 [xfs] | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404014] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404017] [<ffffffff8109b6e4>] worker_thread+0x224/0x4d0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404018] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404020] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404021] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404024] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404026] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.404045] INFO: task docker:2571 blocked for more than 120 seconds. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.411764] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.418839] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428167] docker D ffff882276a7fa78 0 2571 1 0x00000002 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428170] ffff882276a7fa78 0000000000000005 ffff882299d20000 ffff88227ee4e200 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428172] ffff882276a80000 ffff882276a7fbd0 ffff882276a7fbc8 ffff88227ee4e200 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428174] ffffffffffffffff ffff882276a7fa90 ffffffff818404e5 7fffffffffffffff | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428176] Call Trace: | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428180] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428187] [<ffffffff81843635>] schedule_timeout+0x1b5/0x270 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428191] [<ffffffff810ac1c4>] ? check_preempt_curr+0x54/0x90 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428192] [<ffffffff810ac219>] ? ttwu_do_wakeup+0x19/0xe0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428194] [<ffffffff810ac37d>] ? ttwu_do_activate.constprop.86+0x5d/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428196] [<ffffffff81840f43>] wait_for_completion+0xb3/0x140 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428197] [<ffffffff810ad200>] ? wake_up_q+0x70/0x70 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428200] [<ffffffff8109c17d>] flush_work+0x10d/0x1c0 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428205] [<ffffffff81098340>] ? destroy_worker+0x90/0x90 | |
Mar 16 02:42:47 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428233] [<ffffffffc04a01bb>] xlog_cil_force_lsn+0x8b/0x210 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428250] [<ffffffffc049e355>] _xfs_log_force+0x85/0x2a0 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428254] [<ffffffff811f0454>] ? kmem_cache_free+0x1d4/0x1e0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428268] [<ffffffffc049e596>] xfs_log_force+0x26/0x90 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428283] [<ffffffffc0495815>] xfs_fs_sync_fs+0x25/0x50 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428290] [<ffffffffc03aa379>] aufs_sync_fs+0xa9/0x150 [aufs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428293] [<ffffffff81245871>] sync_filesystem+0x71/0xa0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428295] [<ffffffff812131c7>] generic_shutdown_super+0x27/0x100 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428298] [<ffffffff81213522>] kill_anon_super+0x12/0x20 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428301] [<ffffffffc03a9e74>] aufs_kill_sb+0x124/0x160 [aufs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428303] [<ffffffff812471a7>] ? pin_kill+0x77/0x110 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428305] [<ffffffff812136f3>] deactivate_locked_super+0x43/0x70 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428307] [<ffffffff81213bcc>] deactivate_super+0x5c/0x60 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428309] [<ffffffff81231baf>] cleanup_mnt+0x3f/0x90 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428311] [<ffffffff81231c42>] __cleanup_mnt+0x12/0x20 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428313] [<ffffffff8109fc71>] task_work_run+0x81/0xa0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428316] [<ffffffff81003242>] exit_to_usermode_loop+0xc2/0xd0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428318] [<ffffffff81003c6e>] syscall_return_slowpath+0x4e/0x60 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428321] [<ffffffff81844793>] int_ret_from_sys_call+0x25/0x93 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.428419] INFO: task filebeat:14831 blocked for more than 120 seconds. | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.436389] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.442075] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451389] filebeat D ffff881f49fe7a98 0 14831 14612 0x00000104 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451392] ffff881f49fe7a98 ffff881f49fe7a78 ffff882299cf7000 ffff8800a97a5400 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451393] ffff881f49fe8000 ffff881f49fe7bf0 ffff881f49fe7be8 ffff8800a97a5400 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451395] ffffffffffffffff ffff881f49fe7ab0 ffffffff818404e5 7fffffffffffffff | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451397] Call Trace: | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451399] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451402] [<ffffffff81843635>] schedule_timeout+0x1b5/0x270 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451405] [<ffffffff810ac1f0>] ? check_preempt_curr+0x80/0x90 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451406] [<ffffffff810ac219>] ? ttwu_do_wakeup+0x19/0xe0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451411] [<ffffffff810ac37d>] ? ttwu_do_activate.constprop.86+0x5d/0x70 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451416] [<ffffffff81840f43>] wait_for_completion+0xb3/0x140 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451418] [<ffffffff810ad200>] ? wake_up_q+0x70/0x70 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451421] [<ffffffff8109c17d>] flush_work+0x10d/0x1c0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451423] [<ffffffff81098340>] ? destroy_worker+0x90/0x90 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451442] [<ffffffffc04a01bb>] xlog_cil_force_lsn+0x8b/0x210 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451459] [<ffffffffc049e6ca>] _xfs_log_force_lsn+0x7a/0x340 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451463] [<ffffffff8118fc0e>] ? filemap_fdatawait_range+0x1e/0x30 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451465] [<ffffffff81842922>] ? down_read+0x12/0x30 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451480] [<ffffffffc0480b9d>] xfs_file_fsync+0x11d/0x240 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451483] [<ffffffff812456db>] vfs_fsync_range+0x4b/0xb0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451498] [<ffffffffc0481f77>] xfs_file_write_iter+0x127/0x150 [xfs] | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451501] [<ffffffff8121079b>] new_sync_write+0x9b/0xe0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451504] [<ffffffff81210806>] __vfs_write+0x26/0x40 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451506] [<ffffffff81211189>] vfs_write+0xa9/0x1a0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451508] [<ffffffff81211e45>] SyS_write+0x55/0xc0 | |
Mar 16 02:42:48 allocator-uw1-allocator-v1-a-714m kernel: [ 362.451510] [<ffffffff81844619>] entry_SYSCALL_64_fastpath+0x16/0x8d | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.550631] audit: type=1400 audit(1521168196.135:59): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14952 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.550745] audit: type=1400 audit(1521168196.135:60): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14952 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.550764] audit: type=1400 audit(1521168196.135:61): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14952 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.551205] audit: type=1400 audit(1521168196.135:62): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.551409] audit: type=1400 audit(1521168196.135:63): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:43:16 allocator-uw1-allocator-v1-a-714m kernel: [ 390.551433] audit: type=1400 audit(1521168196.135:64): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14942 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528459] audit: type=1400 audit(1521168256.128:65): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528572] audit: type=1400 audit(1521168256.128:66): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528591] audit: type=1400 audit(1521168256.128:67): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528744] audit: type=1400 audit(1521168256.128:68): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528861] audit: type=1400 audit(1521168256.128:69): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
Mar 16 02:44:16 allocator-uw1-allocator-v1-a-714m kernel: [ 450.528880] audit: type=1400 audit(1521168256.128:70): apparmor="DENIED" operation="ptrace" profile="docker-default" pid=14950 comm="metricbeat" requested_mask="trace" denied_mask="trace" peer="unconfined" | |
[ 482.413186] INFO: task kworker/u44:2:249 blocked for more than 120 seconds. | |
[ 482.420294] Not tainted 4.4.0-109-generic #132-Ubuntu | |
[ 482.425980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 [ 482.433997] INFO: task kworker/5:1H:762 blocked for more than 120 seconds. | |
allocator-uw1-al[ 482.442373] Not tainted 4.4.0-109-generic #132-Ubuntu | |
[ 482.449440] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
locator-v1-a-714[ 482.457534] INFO: task kworker/0:1H:767 blocked for more than 120 seconds. | |
m kernel: [ 482[ 482.465744] Not tainted 4.4.0-109-generic #132-Ubuntu | |
.413186] INFO: t[ 482.472816] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
ask kworker/u44:[ 482.482203] INFO: task kworker/5:2:1137 blocked for more than 120 seconds. | |
2:249 blocked fo[ 482.490510] Not tainted 4.4.0-109-generic #132-Ubuntu | |
r more than 120 [ 482.497581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
seconds. | |
Mar 16[ 482.507110] INFO: task kworker/2:1H:1592 blocked for more than 120 seconds. | |
02:44:48 alloca[ 482.515366] Not tainted 4.4.0-109-generic #132-Ubuntu | |
tor-uw1-allocato[ 482.522455] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
r-v1-a-714m kernel: [ 482.420294] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.425980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433918] kworker/u44:2 D ffff8800360d7be8 0 249 2 0x00000000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433928] Workqueue: nvme nvme_dev_scan [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433930] ffff8800360d7be8 0000000000000000 ffffffff81e13500 ffff882292526200 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433933] ffff8800360d8000 ffff8822917ab8e0 0000000000000000 0000000000001000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433934] ffff882292b3dd00 ffff8800360d7c00 ffffffff818404e5 ffff8822917ab430 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433936] Call Trace: | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433942] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433946] [<ffffffff813d5767>] blk_mq_freeze_queue_wait+0x57/0xc0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433951] [<ffffffff810c4eb0>] ? wake_atomic_t_function+0x60/0x60 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433954] [<ffffffff813d71da>] blk_mq_freeze_queue+0x1a/0x20 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433956] [<ffffffffc0025644>] nvme_revalidate_disk+0x144/0x460 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433961] [<ffffffff8124dab8>] revalidate_disk+0x28/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433963] [<ffffffffc00259a5>] nvme_validate_ns+0x45/0x240 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433966] [<ffffffffc00262a1>] nvme_scan_namespaces+0xc1/0x330 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433969] [<ffffffff810ab6e5>] ? resched_curr+0x65/0xc0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433971] [<ffffffffc0027c1f>] ? nvme_async_event_work+0x7f/0xc0 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433974] [<ffffffffc0027277>] nvme_dev_scan+0x27/0x80 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433977] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433980] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433981] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433983] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433985] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433988] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433990] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.433997] INFO: task kworker/5:1H:762 blocked for more than 120 seconds. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.442373] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.449440] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457381] kworker/5:1H D ffff882290c67b18 0 762 2 0x00000000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457418] Workqueue: xfs-log/dm-1 xfs_log_worker [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457421] ffff882290c67b18 00000021eb016745 ffff882299dd7000 ffff882290764600 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457424] ffff882290c68000 ffff882290c67c78 ffff882290c67c70 ffff882290764600 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457427] ffffffffffffffff ffff882290c67b30 ffffffff818404e5 7fffffffffffffff | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457429] Call Trace: | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457433] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457437] [<ffffffff81843635>] schedule_timeout+0x1b5/0x270 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457439] [<ffffffff810ac1f0>] ? check_preempt_curr+0x80/0x90 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457440] [<ffffffff810ac219>] ? ttwu_do_wakeup+0x19/0xe0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457442] [<ffffffff810acdc9>] ? try_to_wake_up+0x49/0x3f0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457445] [<ffffffff81840f43>] wait_for_completion+0xb3/0x140 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457446] [<ffffffff810ad200>] ? wake_up_q+0x70/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457448] [<ffffffff8109c17d>] flush_work+0x10d/0x1c0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457450] [<ffffffff81098340>] ? destroy_worker+0x90/0x90 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457468] [<ffffffffc04a01bb>] xlog_cil_force_lsn+0x8b/0x210 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457470] [<ffffffff81099359>] ? __queue_work+0x139/0x3c0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457472] [<ffffffff810ba5b5>] ? put_prev_entity+0x35/0x7d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457487] [<ffffffffc049e355>] _xfs_log_force+0x85/0x2a0 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457491] [<ffffffff8102d66c>] ? __switch_to+0x1dc/0x5c0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457505] [<ffffffffc049e596>] xfs_log_force+0x26/0x90 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457518] [<ffffffffc049e624>] xfs_log_worker+0x24/0x50 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457521] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457523] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457525] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457526] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457527] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457530] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457532] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.457534] INFO: task kworker/0:1H:767 blocked for more than 120 seconds. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.465744] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.472816] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482140] kworker/0:1H D ffff882291167b68 0 767 2 0x00000000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482145] Workqueue: kblockd blk_mq_timeout_work | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482146] ffff882291167b68 4544006963703d4d ffffffff81e13500 ffff882290760000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482150] ffff882291168000 ffff8822994eb204 ffff882290760000 00000000ffffffff | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482151] ffff8822994eb208 ffff882291167b80 ffffffff818404e5 ffff8822994eb200 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482153] Call Trace: | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482155] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482157] [<ffffffff8184078e>] schedule_preempt_disabled+0xe/0x10 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482159] [<ffffffff818423c9>] __mutex_lock_slowpath+0xb9/0x130 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482161] [<ffffffff8184245f>] mutex_lock+0x1f/0x30 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482164] [<ffffffffc0027f90>] nvme_dev_disable+0x50/0x470 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482166] [<ffffffff813d69a7>] ? blk_mq_run_hw_queue+0x77/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482169] [<ffffffff81560b2c>] ? __dev_printk+0x3c/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482171] [<ffffffff81560f1c>] ? dev_warn+0x6c/0x90 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482173] [<ffffffffc0028552>] nvme_timeout+0xc2/0x1c0 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482175] [<ffffffff810b7eeb>] ? dequeue_entity+0x41b/0xa80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482177] [<ffffffff813d686f>] blk_mq_rq_timed_out+0x2f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482179] [<ffffffff813d68fe>] blk_mq_check_expired+0x4e/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482180] [<ffffffff813d9508>] bt_for_each+0xd8/0xe0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482181] [<ffffffff813d68b0>] ? blk_mq_rq_timed_out+0x70/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482183] [<ffffffff813d68b0>] ? blk_mq_rq_timed_out+0x70/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482184] [<ffffffff813d9d17>] blk_mq_queue_tag_busy_iter+0x47/0xc0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482186] [<ffffffff813d55cc>] blk_mq_timeout_work+0xdc/0x180 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482188] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482190] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482192] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482193] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482195] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482198] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482199] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.482203] INFO: task kworker/5:2:1137 blocked for more than 120 seconds. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.490510] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.497581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506903] kworker/5:2 D ffff882297287958 0 1137 2 0x00000000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506928] Workqueue: xfs-cil/dm-1 xlog_cil_push_work [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506930] ffff882297287958 dead000000000200 ffff882293acaa00 ffff88228f4cc600 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506932] ffff882297288000 ffff8822902d5290 ffff8822902d5298 ffff881f591fdf20 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506934] 0000000000000000 ffff882297287970 ffffffff818404e5 ffff8822902d5000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506935] Call Trace: | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506938] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506941] [<ffffffff816b0558>] md_flush_request+0x78/0x130 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506944] [<ffffffff810c4eb0>] ? wake_atomic_t_function+0x60/0x60 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506947] [<ffffffffc000839d>] raid0_make_request+0x21d/0x230 [raid0] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506949] [<ffffffff816ab830>] md_make_request+0x100/0x230 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506951] [<ffffffff816be304>] ? dm_make_request+0x74/0xc0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506953] [<ffffffff813cb9ff>] generic_make_request+0x10f/0x2c0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506956] [<ffffffff813c325e>] ? bvec_alloc+0x5e/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506958] [<ffffffff813cbc26>] submit_bio+0x76/0x170 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506974] [<ffffffffc047a69e>] _xfs_buf_ioapply+0x2de/0x490 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.506991] [<ffffffffc049b5cb>] ? xlog_bdstrat+0x2b/0x60 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507006] [<ffffffffc047be74>] xfs_buf_submit+0x64/0x1c0 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507021] [<ffffffffc049b5cb>] xlog_bdstrat+0x2b/0x60 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507036] [<ffffffffc049d475>] xlog_sync+0x2d5/0x400 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507050] [<ffffffffc049d616>] xlog_state_release_iclog+0x76/0xc0 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507064] [<ffffffffc049e0b2>] xlog_write+0x5d2/0x700 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507079] [<ffffffffc049f93b>] xlog_cil_push+0x22b/0x3f0 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507093] [<ffffffffc049fb15>] xlog_cil_push_work+0x15/0x20 [xfs] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507095] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507097] [<ffffffff8109b6e4>] worker_thread+0x224/0x4d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507099] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507101] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507102] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507105] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507107] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.507110] INFO: task kworker/2:1H:1592 blocked for more than 120 seconds. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.515366] Not tainted 4.4.0-109-generic #132-Ubuntu | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.522455] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531781] kworker/2:1H D ffff882290defb68 0 1592 2 0x00000000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531788] Workqueue: kblockd blk_mq_timeout_work | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531791] ffff882290defb68 4544006963703d4d ffff882299cf1c00 ffff88227ece8000 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531792] ffff882290df0000 ffff8822994eb204 ffff88227ece8000 00000000ffffffff | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531794] ffff8822994eb208 ffff882290defb80 ffffffff818404e5 ffff8822994eb200 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531798] Call Trace: | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531802] [<ffffffff818404e5>] schedule+0x35/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531806] [<ffffffff8184078e>] schedule_preempt_disabled+0xe/0x10 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531808] [<ffffffff818423c9>] __mutex_lock_slowpath+0xb9/0x130 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531811] [<ffffffff8184245f>] mutex_lock+0x1f/0x30 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531815] [<ffffffffc0027f90>] nvme_dev_disable+0x50/0x470 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531816] [<ffffffff813d69a7>] ? blk_mq_run_hw_queue+0x77/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531820] [<ffffffff81560b2c>] ? __dev_printk+0x3c/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531822] [<ffffffff81560f1c>] ? dev_warn+0x6c/0x90 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531824] [<ffffffffc0028552>] nvme_timeout+0xc2/0x1c0 [nvme] | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531827] [<ffffffff810b7eeb>] ? dequeue_entity+0x41b/0xa80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531828] [<ffffffff813d686f>] blk_mq_rq_timed_out+0x2f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531830] [<ffffffff813d68fe>] blk_mq_check_expired+0x4e/0x80 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531832] [<ffffffff813d9508>] bt_for_each+0xd8/0xe0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531833] [<ffffffff813d68b0>] ? blk_mq_rq_timed_out+0x70/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531835] [<ffffffff813d68b0>] ? blk_mq_rq_timed_out+0x70/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531836] [<ffffffff813d9d17>] blk_mq_queue_tag_busy_iter+0x47/0xc0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531838] [<ffffffff813d55cc>] blk_mq_timeout_work+0xdc/0x180 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531841] [<ffffffff8109b1a5>] process_one_work+0x165/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531843] [<ffffffff8109b50b>] worker_thread+0x4b/0x4d0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531845] [<ffffffff8109b4c0>] ? process_one_work+0x480/0x480 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531847] [<ffffffff810a1845>] kthread+0xe5/0x100 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531849] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531852] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70 | |
Mar 16 02:44:48 allocator-uw1-allocator-v1-a-714m kernel: [ 482.531854] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment