SAN and ibdata files

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 Dan Nelson

Back
In the last episode (Oct 08), Ace said:
> On 10/7/07, Dan Nelson <dnelson@(protected)> wrote:
> > In the last episode (Oct 06), Ace said:
> > > 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.
>
> 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?

That looks like NAS (Network Attached Storage - connecting to a remote
server's exported filesystems using NFS, SMB, etc), not SAN (Storage
Area Network - connecting to remote disk arrays using fibre-channel).

no_root_squash is a Linux NFS server option. Your nfs mountpoint is
/opsolnfs/, so I guess you're running OpenSolaris? You'll want to use
the root=access_list option (see the share_nfs manpage for syntax and
examples).

Other options: 1) log directly into your NAS server as root and chown
the files directly. 2) delete the files you created and re-copy them,
making sure you copy them as the mysql user itself so the files get the
right ownership when they are created.

--
Dan Nelson
dnelson@(protected)

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql@(protected)