You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello there,
I am not sure if I use it wrong but when I turn on the RocksDB use_direct_reads, this SIGSEGV bug will show up when open the db. I used version 5.9.2. Hope someone can shed some light on this. Thanks!
Expected behavior
The RocksDB direct I/O mode work fine.
Actual behavior
This SIGSEGV appears when open db.
Steps to reproduce the behavior
set use_direct_reads = true in options.h file.
invoke DB::Open api
coredump
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fa23a22d810 in _IO_sgetn_internal () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fa23b44aa80 (LWP 38038))]
(gdb) bt
#0 0x00007fa23a22d810 in _IO_sgetn_internal () from /lib64/libc.so.6
#1 0x00007fa23a22ac0e in fread_unlocked () from /lib64/libc.so.6
#2 0x000000000074b25a in rocksdb::PosixSequentialFile::Read (this=0x28e05a0, n=8192, result=0x7ffefb636f30, scratch=0x2864000 "") at env/io_posix.cc:159
#3 0x000000000073f500 in rocksdb::ReadFileToString (env=<optimized out>, fname=..., data=data@entry=0x7ffefb637060) at env/env.cc:297
#4 0x00000000007198c5 in rocksdb::VersionSet::Recover (this=0x26ca2c0, column_families=..., read_only=read_only@entry=false) at db/version_set.cc:2817
#5 0x0000000000689018 in rocksdb::DBImpl::Recover (this=this@entry=0x28ce000, column_families=..., read_only=read_only@entry=false, error_if_log_file_exist=error_if_log_file_exist@entry=false,
error_if_data_exists_in_logs=error_if_data_exists_in_logs@entry=false) at db/db_impl_open.cc:361
VersionSet::Recover -> ReadFileToString -> Read
If use direct reads, NewSequentialFile function will init fd, but FILE ptr is NULL. When invoke SequentialFile‘s Read, it will invoke fread_unlocked(scratch, 1, n, file_), but file_ is NULL, crash here!
The text was updated successfully, but these errors were encountered:
Hello there,
I am not sure if I use it wrong but when I turn on the RocksDB use_direct_reads, this SIGSEGV bug will show up when open the db. I used version 5.9.2. Hope someone can shed some light on this. Thanks!
Expected behavior
The RocksDB direct I/O mode work fine.
Actual behavior
This SIGSEGV appears when open db.
Steps to reproduce the behavior
coredump
rocksdb log
creash reason
VersionSet::Recover -> ReadFileToString -> Read
If use direct reads, NewSequentialFile function will init fd, but FILE ptr is NULL. When invoke SequentialFile‘s Read, it will invoke fread_unlocked(scratch, 1, n, file_), but file_ is NULL, crash here!
The text was updated successfully, but these errors were encountered: