May 13, 201511 yr Unraid 6 beta 15 here. Suddenly my all my dockers became offline. This is the second time it happens for the last 3 days. A restart of the array solves it. Here is what I had in my log. May 14 00:33:13 UNRAID kernel: BTRFS (device loop0): parent transid verify failed on 1008828416 wanted 178026 found 176354 May 14 00:33:13 UNRAID kernel: BTRFS (device loop0): parent transid verify failed on 1008828416 wanted 178026 found 176354 The above message was generated million times. What does it mean? The cache disk where the docker.img resides is RFS formatted. A smart test was performed showing no issues. Searched the board and couldn't managed to find similar complain from other users.
May 13, 201511 yr Author Just restarted again and I have a different message in my syslog (attached) this time. May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 40191112 off 13086720 csum 4075985030 expected csum 3722458094 May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 40191112 off 13086720 csum 4075985030 expected csum 3722458094 May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 31910 off 922968064 csum 2992561721 expected csum 3393297930 May 14 01:56:59 UNRAID kernel: BTRFS info (device loop0): csum failed ino 31910 off 922968064 csum 2992561721 expected csum 3393297930 syslog.zip
May 13, 201511 yr quick search on my graylog server that my unraid logs get pushed to shows 116 instances of UNRAID kernel: BTRFS (device loop0): parent transid verify failed on ....... since 3rd march of this year and 6 of the csum errors in the same period.
May 14, 201511 yr Author Does it mean it is a bug in beta 15? Haven't noticed such a behavior of beta 14. Edited: The problem gets deeper. Now I am unable to use the cache drive as it gets read only almost immediately after a restart and BTRFS-scrub tools are unable to start. ERROR: scrubbing /var/lib/docker failed for device id 1 (Read-only file system) scrub canceled for d2d1ad6d-a902-4299-a60c-d4f6a31397ce scrub started at Thu May 14 09:14:51 2015 and was aborted after 0 seconds total bytes scrubbed: 0.00B with 0 errors Edited: Restarted again the whole server and went directly to docker settings. Ran scrub, and here is the output: ERROR: There are uncorrectable errors. scrub device /dev/loop0 (id 1) done scrub started at Thu May 14 09:27:07 2015 and finished after 1 seconds data_extents_scrubbed: 241775 tree_extents_scrubbed: 25372 data_bytes_scrubbed: 3474448384 tree_bytes_scrubbed: 415694848 read_errors: 0 csum_errors: 2 verify_errors: 0 no_csum: 320 csum_discards: 267533 super_errors: 0 malloc_errors: 0 uncorrectable_errors: 2 unverified_errors: 0 corrected_errors: 0 last_physical: 6480199680
Archived
This topic is now archived and is closed to further replies.