Bug 35703 - Pool 'ztest' has encountered an uncorrectable I/O failure
Summary: Pool 'ztest' has encountered an uncorrectable I/O failure
Status: CLOSED WORKSFORME
Alias: None
Product: Sisyphus
Classification: Development
Component: zfs-utils (show other bugs)
Version: unstable
Hardware: all Linux
: P3 normal
Assignee: Anton Farygin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-03 12:56 MSK by Antonov Alexander
Modified: 2018-12-05 10:54 MSK (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Antonov Alexander 2018-12-03 12:56:00 MSK 
Ошибка возникает на std-def и un-def.
[root@server-x86-64 ~]#  zfs list
NAME          USED  AVAIL  REFER  MOUNTPOINT
pool0         134K  14,4G    24K  /pool0
pool0/data     24K  14,4G    24K  /pool0/data
pool0/files    24K  14,4G    24K  /pool0/files
[root@server-x86-64 ~]# ztest
loading space map for vdev 0 of 1, metaslab 24 of 62 ...
loading space map for vdev 0 of 1, metaslab 26 of 62 ...
loading space map for vdev 0 of 1, metaslab 49 of 62 ...
24.1M completed (  22MB/s) estimated time remaining: 0hr 00min 00sec        error: Pool 'ztest' has encountered an uncorrectable I/O failure and the failure mode property for this pool is set to panic.
/sbin/ztest[0x408f3c]
/lib64/libpthread.so.0(+0x12890)[0x7fae45211890]
/lib64/libc.so.6(gsignal+0x10b)[0x7fae450767ab]
/lib64/libc.so.6(abort+0x121)[0x7fae45061515]
/lib64/libzpool.so.2(+0x3b72f)[0x7fae4563a72f]
/lib64/libzpool.so.2(panic+0x8c)[0x7fae4563a7bc]
/lib64/libzpool.so.2(zio_suspend+0xb9)[0x7fae4572e7e9]
/lib64/libzpool.so.2(+0x13084b)[0x7fae4572f84b]
/lib64/libzpool.so.2(zio_execute+0x8d)[0x7fae4572cd1d]
/lib64/libzpool.so.2(+0x3c4f6)[0x7fae4563b4f6]
/lib64/libzpool.so.2(zk_thread_helper+0x12c)[0x7fae45638b7c]
/lib64/libpthread.so.0(+0x7ed3)[0x7fae45206ed3]
/lib64/libc.so.6(clone+0x3f)[0x7fae451381cf]
child died with signal 6
Comment 1 Anton Farygin 2018-12-05 10:54:48 MSK 
Увеличение объёма оперативной памяти поможет обойти эту ошибку.
На 16Gb у меня не вылезло, возможно можно меньше указать.