What am I doing wrong with MOUNT?
Alex Shaw
alex.shaw at bulletonline.com
Mon Feb 28 19:10:02 GMT 2005
just a thought, if you need more room for you mysql db's why not mount the new drive as /db for example and just change the datadir variable in your my.cnf so your not using the /var drive for databases .... ??
On Mon, 28 Feb 2005 09:24:48 -0500
James Alexander Cook <james.cook at utoronto.ca> wrote:
> On Mon, Feb 28, 2005 at 12:43:44AM -0800, Gerald Lightsey wrote:
>
> <snip>
> > I mounted the new drive 1 to a temporary mount point and used the cp command
> > to copy each directory in /var to the drive. I looked in all the new/old
> > directories at the temporary mount point using ls -F and everything appeared
> > to be there at the file level. I used the umount command to unmount the new
> > drive/partition from the temporary mount point and remounted it at /var. I
>
> sysinstall usually gives /var its own partition when you install FreeBSD, so
> you probably already had something mounted on /var before you started moving
> things over. Try unmounting the thing that was previously mounted on /var
> before mounting the new disk; I'm not sure how mount deals with more than one
> filesystem mounted at the same place. If that doesn't work, send the output of
> ``df'' to the list after unmounting the old /var and mounting the new one.
>
> Oh, and don't forget to update /etc/fstab once you get everything working.
>
> > opened MySQL and created the named database I wanted and again started to
> > collect the data from the CD by directing the .SQL file data to my database.
> > Again, just like it did originally, after several minutes of creating tables
> > the system reported that it had run out of space.
> >
> > My surprise is that every indication I get after I regain control of the
> > system is that the database tables are being built within the original /var
> > directory structure rather than the 120gb drive mounted on the /var
> > mountpoint. If I use the df command while drive 1 is mounted it shows that
> > /var on disk 0 is full and /var on disk 1 just has whatever I copied onto
> > the drive when it was mounted to a temporary mount point. Also by
> > experimentation/confirmation I find that simply creating a couple of new
> > databases within MySQL while drive 1 is mounted on /var shows that the
> > databases have been created on the original /var on disk 0 as directories
> > after disk 1 is unmounted.
> >
> > What am I doing wrong or what don't I understand about a drive being mounted
> > on /var where data is being written underneath it to the original
> > /var/db/mysql/mydatabasename on disk 0 rather than onto the mounted disk 1?
> >
> > Thanks,
> >
> > Gerald
> _______________________________________________
> freebsd-newbies at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-newbies
> To unsubscribe, send any mail to "freebsd-newbies-unsubscribe at freebsd.org"
>
More information about the freebsd-newbies
mailing list