FreeBSD Port: mysql-server-4.0.20
thelen at ccgis.de
Wed Jul 14 06:02:37 PDT 2004
Christoph Bodner wrote:
> Dear package-maintainers of the MySQL-server!
> I would like to inform you of a potential problem when using
> "/var/db/mysql" as the data folder. Usually in a standard installation,
> during slicing and partitioning the disk layout, "/var" belongs to
> partition "e", which is, e.g., only 256 MB large as opposed to
> partition "g" which can hold many GigaBytes. The folllowing listing is
> a "df" output of my server:
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/ar0s1a 128990 47748 70924 40% /
> /dev/ar0s1f 257998 8 237352 0% /tmp
> /dev/ar0s1g 77123102 27117646 43835608 38% /usr
> /dev/ar0s1e 257998 1034 236326 0% /var
> procfs 4 4 0 100% /proc
> Therefore, I am forced to reconfigure this for a real-world-mission
> where MySQL tables require much more space than reservered for partition
> "e". Maybe, "/usr/home/mysql" or "/usr/local/mysql" would be a better
> location for the data dictionary of MySQL.
> Kind regards,
> Christoph Bodner
> Innsbruck (Austria)
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
At first glance, I would agree that the standard /var partition size
is not suitable for using databases. That was, what I first thought.
The same is true for postgresql. But honestly I don't think, that
/usr/xxx/mysql or .../pgsql is a good solution. I use symbolic links
in /var and move the databases to a 5th partition h, which I mount as
/data. That works fine. Another solution would be to just use a bigger
/var partition and a third way would be to use a separate harddisk,
which is for bigger databases the best solution annyway. If you plan
to setup a new server for database purposes, I think you do not want
to just accept the defaults. Otherwise I suggest to use symbolic links.
More information about the freebsd-ports