IO Worker #2' panicked at 'DB flush failed'

[aleksey-makarov]

I'm running:

• Which Parity version?: Parity/v1.8.5-beta-54bae9a0f-20171228/x86_64-linux-gnu/rustc1.22.1
• Which operating system?: Linux Arch
• How installed?: via installer
• Are you fully synchronized?: no
• Did you try to restart the node?: yes, it works

I've got a sigsegv, see the attachment log.txt

[aleksey-makarov]

#7334 looks the same

[aleksey-makarov]

fsck.ext4 reported some errors. I think it should not oops anyway.

[aleksey-makarov]

have got it agan, same setup

● parity.service - Parity Daemon
   Loaded: loaded (/usr/lib/systemd/user/parity.service; disabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2018-01-02 15:04:46 +06; 2h 41min ago
  Process: 1079 ExecStart=/usr/bin/parity (code=killed, signal=ABRT)
 Main PID: 1079 (code=killed, signal=ABRT)

янв 02 15:04:18 lemon parity[1079]: 2018-01-02 15:04:18  Syncing snapshot 396/720  #4489346   25/25 peers      1 MiB chain   67 MiB db  0 bytes queue   10 KiB sync  R
янв 02 15:04:36 lemon parity[1079]: ====================
янв 02 15:04:36 lemon parity[1079]: stack backtrace:
янв 02 15:04:36 lemon parity[1079]:    0:     0x562507b7d35c - <unknown>
янв 02 15:04:36 lemon parity[1079]: Thread 'IO Worker #2' panicked at 'DB flush failed.: "Corruption: block checksum mismatch"', src/libcore/result.rs:906
янв 02 15:04:36 lemon parity[1079]: This is a bug. Please report it at:
янв 02 15:04:36 lemon parity[1079]:     https://github.com/paritytech/parity/issues/new
янв 02 15:04:45 lemon systemd-coredump[1628]: Process 1079 (parity) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 1118:
                                                 #0  0x00007ff867e04860 n/a (n/a)
янв 02 15:04:46 lemon systemd[623]: parity.service: Main process exited, code=killed, status=6/ABRT
янв 02 15:04:46 lemon systemd[623]: parity.service: Failed with result 'signal'.

[5chdn]

Thanks for your report. Let's track it in #7334