Skip to Main Content

Hardware

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

key block corrupted for file against 50407?

3850163Dec 12 2018 — edited Dec 12 2018

Hi everyone,

I am using vdbench 50407 to verify if files created by vdbench are consistent. The 2 parameter files as below.

1. For file creation

journal=noflush

validate=yes

fsd=fsd1,anchor=/mnt/test,depth=1,width=1,files=10,size=128k,openflags=o_direct

fwd=fwd1,fsd=fsd1,operation=read,fileio=sequential,fileselect=random,threads=1

rd=rd1,fwd=fwd1,fwdrate=max,format=yes,elapsed=10,interval=1

2. For file validation

data_errors=1

journal=(recover,only)

fsd=fsd1,anchor=/mnt/test,depth=1,width=1,files=10,size=128k,openflags=o_direct

fwd=fwd1,fsd=fsd1,operation=read,fileio=sequential,fileselect=random,threads=1

rd=rd1,fwd=fwd1,fwdrate=max,format=no,elapsed=10,interval=1

With the second parameter file, I got following errors that the files are corrupted. Is there any hint why such error happened? Thanks a lot for any help.

#########################

Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Vdbench distribution: vdbench50407 Tue June 05  9:49:29 MDT 2018

For documentation, see 'vdbench.pdf'.

16:51:18.654 input argument scanned: '-fparam-rd-test'

16:51:18.784 Anchor size: anchor=/mnt/test: dirs:            1; files:           10; bytes:     1.250m (1,310,720)

16:51:19.074 Starting slave: /root/vdbench/vdbench SlaveJvm -m localhost -n localhost-10-181212-16.51.18.608 -l localhost-0 -p 5570 

16:51:19.606 All slaves are now connected

16:51:20.129 localhost-0: 16:51:20.126 Starting journal recovery for fsd1

16:51:20.238 localhost-0: 16:51:20.234 Completed journal recovery for fsd1. Starting data validation.

16:51:21.002 Starting RD=journal_recovery; elapsed=(none); fwdrate=max. For loops: None

16:51:21.283 localhost-0: 16:51:21.282 setBlockBad(): more than 1%% of the file is marked bad. File no longer will be used: /mnt/test/vdb.1_1.dir/vdb_f0004.file

16:51:21.284 localhost-0: 16:51:21.282 File marked bad: /mnt/test/vdb.1_1.dir/vdb_f0004.file

16:51:21.291 localhost-0: 16:51:21.286

16:51:21.291 localhost-0: 16:51:21.286 Time of first corruption: Wed Dec 12 2018 16:51:21.286 UTC

16:51:21.291 localhost-0: 16:51:21.286

16:51:21.291 localhost-0: 16:51:21.286 At least one Data Validation error has been detected.                             

16:51:21.291 localhost-0: 16:51:21.286

16:51:21.291 localhost-0: 16:51:21.286 Terminology:                                                                      

16:51:21.291 localhost-0: 16:51:21.287 - Data block: a block of xfersize= bytes.                                         

16:51:21.291 localhost-0: 16:51:21.287 - Key block:  the smallest xfersize specified by the user which is the unit of    

16:51:21.291 localhost-0: 16:51:21.287               data that Data Validation keeps track of.                           

16:51:21.292 localhost-0: 16:51:21.287 - Sector:     512 bytes of disk storage, regardless of actual storage sector size.

16:51:21.292 localhost-0: 16:51:21.287 - Lba:        Logical Byte Address, not to be confused with Logical Block Address.

16:51:21.292 localhost-0: 16:51:21.287

16:51:21.292 localhost-0: 16:51:21.287

16:51:21.292 localhost-0: 16:51:21.287 The output starts with a summary of a data block, followed by a summary of each   

16:51:21.292 localhost-0: 16:51:21.287 key block. If all sectors in a key block show a similar type of data corruption   

16:51:21.292 localhost-0: 16:51:21.287 only the FIRST sector of the key block will be reported.                          

16:51:21.292 localhost-0: 16:51:21.287 For all other cases, ALL sectors will be reported.                                

16:51:21.292 localhost-0: 16:51:21.287

16:51:21.292 localhost-0: 16:51:21.287 Contents of the first 32 bytes of each sector:                                    

16:51:21.292 localhost-0: 16:51:21.287

16:51:21.292 localhost-0: 16:51:21.287 Byte 0x00 -  0x07: Byte offset of this disk block

16:51:21.293 localhost-0: 16:51:21.287 Byte 0x08 -  0x0f: Timestamp: number of milliseconds since 1/1/1970

16:51:21.293 localhost-0: 16:51:21.287 Byte 0x10        : Data Validation key from 1 - 126

16:51:21.293 localhost-0: 16:51:21.287 Byte 0x11        : Checksum of timestamp

16:51:21.293 localhost-0: 16:51:21.287 Byte 0x12 -  0x13: Reserved

16:51:21.293 localhost-0: 16:51:21.288 Byte 0x14 -  0x1b: SD or FSD name in ASCII hexadecimal

16:51:21.293 localhost-0: 16:51:21.288 Byte 0x1c -  0x1f: Owner ID when written

16:51:21.293 localhost-0: 16:51:21.288 Byte 0x20 - 0x1ff: 480 bytes of compression data pattern

16:51:21.293 localhost-0: 16:51:21.288

16:51:21.293 localhost-0: 16:51:21.288 On the left:  the data that was expected ('.' marks unknown value).

16:51:21.293 localhost-0: 16:51:21.288 On the right: the data that was found.

16:51:21.293 localhost-0: 16:51:21.288

16:51:21.323 localhost-0: 16:51:21.290

16:51:21.323 localhost-0: 16:51:21.290

16:51:21.323 localhost-0: 16:51:21.290

16:51:21.324 localhost-0: 16:51:21.290 Corrupted data block for fsd=fsd1,file=/mnt/test/vdb.1_1.dir/vdb_f0004.file; file lba: 0x00000000 xfersize=4096

16:51:21.324 localhost-0: 16:51:21.290

16:51:21.324 localhost-0: 16:51:21.290 Data block has 1 key block(s) of 4096 bytes each.

16:51:21.324 localhost-0: 16:51:21.290 All key blocks are corrupted.

16:51:21.324 localhost-0: 16:51:21.290 Key block lba: 0x00080000

16:51:21.324 localhost-0: 16:51:21.291    Key block of 4,096 bytes has 8 512-byte sectors.

16:51:21.324 localhost-0: 16:51:21.291    Timeline:

16:51:21.324 localhost-0: 16:51:21.295    Wed Dec 12 2018 16:50:42.341 UTC Sector last written. (As found in the first corrupted sector, timestamp is taken just BEFORE the actual write).

16:51:21.324 localhost-0: 16:51:21.295    Wed Dec 12 2018 16:51:21.277 UTC Key block first found to be corrupted during a workload requested read.

16:51:21.324 localhost-0: 16:51:21.295

16:51:21.324 localhost-0: 16:51:21.295    All 8 sectors in this key block are corrupted.

16:51:21.325 localhost-0: 16:51:21.295    All corruptions are of the same type:

16:51:21.325 localhost-0: 16:51:21.295    ===> Bad owner id. Expecting 0x18bbd (101309) but found 0x18bbd

16:51:21.325 localhost-0: 16:51:21.295    Only the FIRST sector will be reported:

16:51:21.325 localhost-0: 16:51:21.295

16:51:21.325 localhost-0: 16:51:21.295         Data Validation error for fsd=fsd1; FSD lba: 0x00080000; Key block size: 4096; relative sector in data block: 0x00

16:51:21.325 localhost-0: 16:51:21.295         File name: /mnt/test/vdb.1_1.dir/vdb_f0004.file; file block lba: 0x00000000; bad sector file lba: 0x00000000

16:51:21.325 localhost-0: 16:51:21.321 0x000   00000000 00080000 ........ ........   00000000 00080000 00000167 a353e025

16:51:21.325 localhost-0: 16:51:21.321 0x010   04..0000 31647366 20202020 00000000   04630000 31647366 20202020 00018bbd

16:51:21.325 localhost-0: 16:51:21.321         There are no mismatches in bytes 32-511

16:51:21.326 localhost-0: 16:51:21.324 op: read   lun: /mnt/test/vdb.1_1.dir/vdb_f0004.file lba:            0 0x00000000 xfer:     4096 errno: 60003: '60003            A Data Validation error was discovered'

16:51:21.829

16:51:21.829 'data_errors=1' requested. Abort rd=journal_recovery after last error.

16:51:21.829

java.lang.RuntimeException: 'data_errors=1' requested. Abort rd=journal_recovery after last error.

at Vdb.common.failure(common.java:350)

at Vdb.common.failure(common.java:297)

at Vdb.ErrorLog.countErrorsOnMaster(ErrorLog.java:224)

at Vdb.SlaveOnMaster.processSlave(SlaveOnMaster.java:207)

at Vdb.SlaveOnMaster.run(SlaveOnMaster.java:42)

###################

Comments
Post Details
Added on Dec 12 2018
1 comment
1,003 views