On May 18, 2005, at 3:53 PM, Tom Duerbusch wrote:
Perhaps even copying fstab to fstab.save before changing things. Then
you only have to rename files instead of using "ed" to change lines in
fstab.
Ew.
Just install ned.
Adam
--
Fo
Well, you know what they say...
Great minds
are still sick.
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 05/18/05 3:57 PM >>>
Thanks, Tom. That matches the game plan I just finished writing down.
I decided to do the "cp" instead of "mv," and for exactly the reasons
you describe.
Jon
Thanks, Tom. That matches the game plan I just finished writing down. I
decided to do the "cp" instead of "mv," and for exactly the reasons you
describe.
Jon
Having made many errors
I wouldn't "mv" the directory, just "cp" it.
Since you are creating the directory and contents on new di
I considered that, but since I don't know what sort of magic MySQL
might do behind the scenes, I wasn't too keen on trying it. I hope to start
learning about MySQL soon -- at least enough to be able to poke around in it a
little bit.
Jon
Have you tried mounting your 80GB system some
Having made many errors
I wouldn't "mv" the directory, just "cp" it.
Since you are creating the directory and contents on new disk space,
keep the old directory spinning until you prove to yourself that
everything is working with the LVM version.
It is much easier to recover if you just have
5-865-5940
> --
> From: McKown, John
> Reply To: Linux on 390 Port
> Sent: Wednesday, May 18, 2005 12:38 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Moving /var to LVM
>
> > -Original Message-
> > From: Linux on 390 Port
On Wed, 2005-05-18 at 16:07 -0400, Jon Brock wrote:
> If /var is one file system, I don't like even the suggestion that if,
> say, syslogd filled up /var it could have bad consequences for my
> database.
Ah, I dig. I recall an unpleasant time of it once when /var/mail
suddenly stuffed. Thanks.
It just gives me the willies due to a bad experience I had when trying to
resize /var not long ago. (See my message to Adam.) As long as the MySQL is
in a separate actual file system it shouldn't be too bad. If /var is one file
system, I don't like even the suggestion that if, say, syslogd fi
your cooperation."
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Jon Brock
Sent: Wednesday, May 18, 2005 12:50 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Moving /var to LVM
H. That may be the best idea yet. I was wantin
On Wed, 2005-05-18 at 15:25 -0400, Jon Brock wrote:
> MySQL, which defaults to placing its databases on /var (which I
> consider a Bad Idea, but that's beside the point)
Why is this bad?
--
David Andrews
A. Duda and Sons, Inc.
[EMAIL PROTECTED]
---
50 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Moving /var to LVM
H. That may be the best idea yet. I was wanting to avoid
moving the existing MySQL stuff, but the more I think about it, the
better this sounds.
Thanks,
Jon
You can put your LVM at /var/lib/mysql instead of just
That's reassuring to know (and I'm saving your email). The time I ended up
reloading the system I was trying to resize /var. I took it down to
single-user and issued the umount, which barfed on me (fuser said that "mount"
had /var. Joy.) Anyway, a lazy unmount worked, but shortly after I tri
H. That may be the best idea yet. I was wanting to avoid moving
the existing MySQL stuff, but the more I think about it, the better this sounds.
Thanks,
Jon
You can put your LVM at /var/lib/mysql instead of just /var.
On May 18, 2005, at 2:25 PM, Jon Brock wrote:
We have a vendor installing a product on a zLinux image. This
product uses MySQL, which defaults to placing its databases on /var
(which I consider a Bad Idea, but that's beside the point).
Because of this, they need 80 GB for /var. I have an 80 G
Quoting Jon Brock <[EMAIL PROTECTED]>:
> We have a vendor installing a product on a zLinux image. This product
> uses
> MySQL, which defaults to placing its databases on /var (which I consider a
> Bad Idea, but that's beside the point). Because of this, they need 80 GB for
> /var. I have
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Jon Brock
> Sent: Wednesday, May 18, 2005 2:26 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Moving /var to LVM
>
>
> We have a vendor installing a product on a zLi
Brock
Sent: Wednesday, May 18, 2005 12:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Moving /var to LVM
We have a vendor installing a product on a zLinux image. This
product uses MySQL, which defaults to placing its databases on /var
(which I consider a Bad Idea, but that's b
Yeah, I know. I'm trying to talk them into changing the location -- I
think it's mainly a matter of editing /etc/my.conf -- but I am not confident of
success.
Jon
We have mysql installed and i have it pointed to /data as it's database. It
can be configured to not put it in /var
--
That's what I had planned on doing, but I'll need to either copy or
move the existing /var data first. The part that kills me is that it is
possible to tell MySQL to put its data somewhere else, but when I reminded the
vendor about the existing file system the response I got was "The de
LINUX-390@VM.MARIST.EDU
<[EMAIL PROTECTED] cc
IST.EDU>
Subject
Moving /var to LVM
05/18/2005 02:2
day, May 18, 2005 12:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Moving /var to LVM
We have a vendor installing a product on a zLinux image. This
product uses MySQL, which defaults to placing its databases on /var
(which I consider a Bad Idea, but that's beside the point). Because
We have a vendor installing a product on a zLinux image. This product
uses MySQL, which defaults to placing its databases on /var (which I consider a
Bad Idea, but that's beside the point). Because of this, they need 80 GB for
/var. I have an 80 GB ext3 file system created in LVM and
22 matches
Mail list logo
