Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• Update one field with more fields from another table
• Getting Identity after INSERT
• ERROR 2002: Can 't connect to local MySQL server through socket
• mysql test 4 1 fails with the gis test
• MySQL Cluster Software
• Downgrade Mysql from 4 to 3 23
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Can 't access mysql after kernel upgrade
• Executing MySQL Commands From Within C Program
• Comparing and writing out BLOBS
• Preventing Duplicate Entries
• FULLTEXT query format question
• Strange behavior, Table Level Permission
• Does the binary log enabling affect the MySQL performances?
• mysql:it 's a db not a dbms how it 's possible?!
• mysql have same function mthod as Oracle decode()
 
SAN and ibdata files

SAN and ibdata files

2007-10-08       - By Ace

 Back
Thanks Dan! We do know the permission problem. We tried chown but got "Not a
owner" error. That is because of "root squashing" in which root becomes
"nobody" when you cd to NFS directory.
   To overcome this we tried adding "no_root_squash" to export file. but
still the error.

I will overcome this somehow.....but my Biggest worry now is - can I
configure Mysql to use SAN location? if not, why?

Thanks,
Rajan
On 10/7/07, Dan Nelson <dnelson@(protected)> wrote:
>
> In the last episode (Oct 06), Ace said:
> > Hi Experts,
> >
> >       You all know the size problems with ibdata and log files. We plan
> to
> > move those files to SAN to have maximum storage possible. We did so with
> > configuration changes in my.cnf files to save log and ibdata files on
> SAN
> > location. But got following error -
> >
> > InnoDB: Unable to lock /opsolnfs/mysql/ibdata1, error: 13
> > InnoDB: Check that you do not already have another mysqld process
> > InnoDB: using the same InnoDB data or log files.
> >
> >        Any concrete steps to overcome this problem? Your input will add
> > value in solving our problem.
>
> $ perror 13
> OS error code  13:  Permission denied
>
> Check permissions on your data directory.
>
> --
>        Dan Nelson
>        dnelson@(protected)
>