Mark Yieh <m...@ozoneonline.com> writes: > Hi everyone, > I'm not sure if this is any cause for concern, but I > recently had to run an fsck due to a power failure > on my base 4.6 i386 box, and I noticed some > unreferenced files from MySQL. > I installed MySQL from packages and followed the > instructions for a secure install. > I'm pretty new to OpenBSD and system administration > in general, so I'm not sure if this is a big issue. > If it's not then is there a way for me to clear these files > so the next time I run fsck I won't see these errors? > > Here is the output from the fsck program: > fragmentation) > ** /dev/rsd0e (NO WRITE) > ** Last Mounted on /tmp > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > UNREF FILE I=8 OWNER=_mysql MODE=100600 > SIZE=0 MTIME=Nov 1 20:55 2009 > CLEAR? no > > UNREF FILE I=9 OWNER=_mysql MODE=100600 > SIZE=0 MTIME=Nov 1 20:55 2009 > CLEAR? no > > UNREF FILE I=10 OWNER=_mysql MODE=100600 > SIZE=0 MTIME=Nov 1 20:55 2009 > CLEAR? no > > UNREF FILE I=11 OWNER=_mysql MODE=100600 > SIZE=0 MTIME=Nov 1 20:55 2009 > CLEAR? no > > UNREF FILE I=12 OWNER=_mysql MODE=100600 > SIZE=0 MTIME=Nov 1 20:55 2009 > CLEAR? no >
Hi, It seems that these unreferenced files are all located in /tmp, I think you can safely run a 'fsck -y /tmp' to fix the issue in the single user mode. > Here's how I start my MySQL daemon. > > if [ -x /usr/local/bin/mysqld_safe ] ; then > su -c mysql root -c '/usr/local/bin/mysqld_safe > /dev/null > 2>&1 &' > echo -n ' mysql' > fi > > I have that in /etc/rc.local. > That was how the MySQL package suggested to start the daemon. > > Thanks for your help and thanks to the OpenBSD team for their time and > effort. > > > -- tamgya |aT| GmAiL |DoT| cOm
