Bug #61250 Warning: option...unsigned value ..._buffer_size

• Submitted: 21 May 2011 5:37
• Modified: 22 May 2011 8:25
• Reporter: Dirk Kolbe
• Status: Duplicate
• Category: MySQL Server: MyISAM storage engine
• Severity: S3 (Non-critical)
• Version: 5.0.67
• OS: Linux
• CPU Architecture: Any

[21 May 2011 5:37] Dirk Kolbe

Description:
if i use: myisamchk --silent --force /var/lib/mysql/DB214015/*.MYI

this is the result:
Warning: option 'key_buffer_size': unsigned value 18446744073709551615 adjusted to 4294963200
Warning: option 'read_buffer_size': unsigned value 18446744073709551615 adjusted to 4294967295
Warning: option 'write_buffer_size': unsigned value 18446744073709551615 adjusted to 4294967295
Warning: option 'sort_buffer_size': unsigned value 18446744073709551615 adjusted to 4294967295

after i check with: myisamchk --no-defaults

character-sets-dir                (No default value)
data-file-length                  0
keys-used                         18446744073709551615
max-record-length                 9223372036854775807
set-auto-increment                0
set-collation                     (No default value)
sort-records                      0
tmpdir                            (No default value)
key_buffer_size                   520192
key_cache_block_size              1024
myisam_block_size                 1024
read_buffer_size                  262136
write_buffer_size                 262136
sort_buffer_size                  2097144
sort_key_blocks                   16
decode_bits                       9
ft_min_word_len                   4
ft_max_word_len                   84
ft_stopword_file                  (No default value)
stats_method                      nulls_unequal

How to repeat:
i can repeat this error on any time on our server

[21 May 2011 7:43] Valeriy Kravchuk

What exact server version, x.y.z, do you use? What do you consider a critical (S1) bug here?

[22 May 2011 6:03] Dirk Kolbe

Mistake: Chance the sverity and add mysql version

[22 May 2011 8:25] Valeriy Kravchuk

Then this is a duplicate of bug #33785. Upgrade to version >- 5.0.87 if you care about these warnings.