Closed homerl closed 3 years ago
Dupe of #7184 maybe?
It's hard to say for certain, but yes this could definitely be a duplicate of#7184 and should be resolved in master by the improvements to zpool import
.
@homerl Recently I've got a pool not being able to import, and i suspect the case may be similar to your case. The pool reported Input/output error but I have no idea which disk is the culprit.
I am curious that by running which command you get to know the disk sddi is exactly the troubling disk? what is the command you run to get the following messages?
zdb -e ost_61 -d -t 1274825 Dataset mos [META], ID 0, cr_txg 4, 492M, 284 objects Dataset ost_61/ost_61 [ZPL], ID 155, cr_txg 1744, 59.3T, 662232 objects Dataset ost_61 [ZPL], ID 51, cr_txg 1, 68.1K, 6 objects Verified large_blocks feature refcount of 1 is correct Verified large_dnode feature refcount of 0 is correct Verified sha512 feature refcount of 0 is correct Verified skein feature refcount of 0 is correct Verified edonr feature refcount of 0 is correct Verified userobj_accounting feature refcount of 2 is correct ----sddh--finish----- ----sddi----- zdb -e ost_61 -d -t 1414018 zdb: can't open 'ost_61': Input/output error zdb -e ost_61 -d -t 1414019 zdb: can't open 'ost_61': Input/output error zdb -e ost_61 -d -t 1414020
@samuelxhu Thank you, Sorry, the resilvering has finished. because it 's 10TB HDD. I just save 0~100M form the issue HDD. Next time if the issue come back, Could I dd some important part from the issue HDD? I'm not sure whether there is a way to take out the important parts of the issue HDD.
@samuelxhu Sorry, I reply wrong. You could get it from zdb man page
-t transaction
Specify the highest transaction to use when searching for uberblocks. See also the -u and -l options for a means to see the
available uberblocks and their associated transaction numbers.
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.
System information
Describe the problem you're observing
When I reboot the server, single zpool could not be mounted.
When I remove single HDD (echo 1 > /sys/class/block/sddi/device/delete) in this zpool , Why the zpool import success ? Thank you.
I found the input / ouput error in sddi , the others is OK.
Describe how to reproduce the problem
Sorry, I just reboot the server, no other operate, after reboot the zpool could not be imported. because it 's the production env, I have to recover the service ASAP. I 'm just save first 100MB for /dev/sddi
Include any warning/errors/backtraces from the system logs