Bug #43506 6.0 crashes when datadir is a symlink that points to nirvana
Submitted: 9 Mar 2009 15:49 Modified: 10 Mar 2009 7:47
Reporter: Andrey Hristov Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: General Severity:S3 (Non-critical)
Version:6.0 OS:Linux
Assigned to: CPU Architecture:Any

[9 Mar 2009 15:49] Andrey Hristov
Description:
I have my /work/var , which is my datadir, poiting to /dev/shm/var. After restart /dev/shm/var is non-existent. 5.1 starts, emits an error and quits, 6.0 segfaults.

andrey@winnie:/work/mysql-server/mysql-5.1-binprot/sql$ 090309 16:46:11 [Warning] Can't create test file /work/var/winnie.lower-test
090309 16:46:11 [Warning] Can't create test file /work/var/winnie.lower-test
./mysqld: Can't change dir to '/work/var/' (Errcode: 2)
090309 16:46:11 [ERROR] Aborting

090309 16:46:11 [Note] ./mysqld: Shutdown complete

andrey@winnie:/work/mysql-server/mysql-6.0/sql$ 090309 16:45:00 [Warning] Can't create test file /work/var/winnie.lower-test
090309 16:45:00 [Warning] Can't create test file /work/var/winnie.lower-test
./mysqld: Can't change dir to '/work/var/' (Errcode: 2)
090309 16:45:00 [ERROR] Aborting

090309 16:45:00 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=20
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 43659 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = (nil) thread_stack 0x40000
./mysqld(my_print_stacktrace+0x32) [0x899df8d]
./mysqld(handle_segfault+0x2cd) [0x83635ec]
[0xb809f400]
./mysqld(Trans_delegate::~Trans_delegate()+0x11) [0x8592ddd]
./mysqld(delegates_destroy()+0x13) [0x8592698]
./mysqld [0x8364fbb]
./mysqld(unireg_abort+0x7d) [0x83654da]
./mysqld(main+0x153) [0x8367f09]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d77685]
./mysqld [0x8279ba1]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
Try 6.0 with a datadir which is symlink that points to nirvana.
[10 Mar 2009 7:47] Sveta Smirnova
Thank you for the report.

This is duplicate of bug #40853