Date: Wed, 14 Jul 2004 08:52:59 +0200 From: Christoph Bodner <christoph.bodner@chello.at> To: ale@FreeBSD.org Cc: ports@FreeBSD.org Subject: FreeBSD Port: mysql-server-4.0.20 Message-ID: <71A4E938-D562-11D8-83F0-000A958EC5D6@chello.at>
next in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71A4E938-D562-11D8-83F0-000A958EC5D6>