On Saturday 03 December 2005 21:35, Larry K wrote:
> Anyone care to post their scipt to back up/compress their database?I
> suppose I could write my own, but why reinvent the wheel? :)
It's not big or clever[0] but this works for me, keeps 7days worth of
compressed + one uncompressed latest b
Great! I have this script up and running already! Thanks for the link.On 12/3/05, Wade Maxfield <[EMAIL PROTECTED]
> wrote:>Anyone care to post their scipt to back up/compress their database?
>I suppose I could write my own, but why reinvent the wheel? :)>>>This is what I use for all my automatic
Anyone care to post their scipt to back up/compress their database?
I suppose I could write my own, but why reinvent the wheel? :)
This is what I use for all my automatic mysql backups (webservers as well)
MySQL Backup Script
http://sourceforge.net/projects/automysqlbackup/
You'll just nee
Anyone care to post their scipt to back up/compress their database? I suppose I could write my own, but why reinvent the wheel? :)On 12/1/05,
Ian Campbell <[EMAIL PROTECTED]> wrote:
On Thu, 2005-12-01 at 15:34 +, Neil Bird wrote:>My box has been in solid use for 9-odd months, but all I
[EMAIL PROTECTED] mythconverg]# ls -al --sort=sizetotal 263544-rw-rw 1 mysql mysql 150737964 Dec 3 21:08 recordedmarkup.MYD-rw-rw 1 mysql mysql 108397568 Dec 3 21:08 recordedmarkup.MYI-rw-rw 1 mysql mysql 2292452 Dec 3 08:58
program.MYD-rw-rw 1 mysql mysql 914760 Dec 3
On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]
> wrote:Can somebody give me an idea of how large a database typically is
after Myth has been used a long while, or how fast it grows? After ~ 1 year my current database size is 78MB, but I only have ~6 or so undeleted programs right now. Gzipped
Ant Daniel wrote:
On 01/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
No doubt most of that is taken up by the "previously recorded" data.
That could probably be reduced to just the series # and epsiode # if it
wasn't for the "forget old" feature. The other thing that a good
clean-up wo
On 01/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> No doubt most of that is taken up by the "previously recorded" data.
> That could probably be reduced to just the series # and epsiode # if it
> wasn't for the "forget old" feature. The other thing that a good
> clean-up would do is che
> chris writes:
c> On Thu, Dec 01, 2005 at 03:22:24PM -0500, Joseph A. Caputo wrote:
>> 56 MB after 3+ years.
c> No doubt most of that is taken up by the "previously recorded" data.
[...]
Not for me. I have 172MB also after 3 years. The
"oldrecorded" and "oldprogram" tables take u
Date: Thu, 1 Dec 2005 15:17:53 -0800
From: andrew matthews <[EMAIL PROTECTED]>
I use XFS it can be both grown and shrunk.
My manpages and google both seem to disagree with you; neither
xfs_growfs nor xfs_admin claim to be able to do this. If you've
successfully shrunken an XFS filesy
I use XFS it can be both grown and shrunk.I nearly lost a disk about 3 months ago, i shrunk the disk size move all the data from that code to the other drives, and then removed the disk, put in a new one, added it in the volume and then grew the partition again. XFS can do it all! :)
_
On Thu, Dec 01, 2005 at 03:22:24PM -0500, Joseph A. Caputo wrote:
> 56 MB after 3+ years.
No doubt most of that is taken up by the "previously recorded" data.
That could probably be reduced to just the series # and epsiode # if it
wasn't for the "forget old" feature. The other thing that a good
c
Cory Papenfuss wrote:
On Thu, 1 Dec 2005, Joseph A. Caputo wrote:
On Wednesday 30 November 2005 23:26, [EMAIL PROTECTED] wrote:
Can somebody give me an idea of how large a database typically is
after Myth has been used a long while, or how fast it grows?
56 MB after 3+ years.
-JAC
On Thu, 1 Dec 2005, Paul K wrote:
There might be rebuild script, but I usually just make a 0 bit length ascii
file with the same name as the non-existing recordings. Then you can remove
them within myth.
My 20 month long database is about 70Mb uncompressed... ?
I don't record all tha
There might be rebuild script, but I usually just make a 0 bit length ascii file with the same name as the non-existing recordings. Then you can remove them within myth. My 20 month long database is about 70Mb uncompressed... ?
PaulOn 12/1/05, Cory Papenfuss <[EMAIL PROTECTED]> wrote:
On Thu, 1 De
On Thu, 1 Dec 2005, Joseph A. Caputo wrote:
On Wednesday 30 November 2005 23:26, [EMAIL PROTECTED] wrote:
Can somebody give me an idea of how large a database typically is
after Myth has been used a long while, or how fast it grows?
56 MB after 3+ years.
-JAC
Timely subject... I just roll
On Wednesday 30 November 2005 23:26, [EMAIL PROTECTED] wrote:
> Can somebody give me an idea of how large a database typically is
> after Myth has been used a long while, or how fast it grows?
56 MB after 3+ years.
-JAC
___
mythtv-users mailing list
myt
On Thursday 01 December 2005 14:19, Greg Grotsky wrote:
> On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > And I won't use reiserfs. Not 3, not 4. Never again.
>
> What's your issue with riserfs? I'm using it on my mythbox and haven't had
> any issues. Is there something I should
On 11/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
And I won't use reiserfs. Not 3, not 4. Never again.
What's your issue with riserfs? I'm using it on my mythbox and
haven't had any issues. Is there something I should be worried
about?
Thanks,
-Greg
__
On Thu, 2005-12-01 at 15:34 +, Neil Bird wrote:
>My box has been in solid use for 9-odd months, but all I do is backup the
> SQL [currently every night, with a back-up file per day of the week; if it's
> going to start getting *really* big I'll have to drop that (it's
> bz-compressed)].
Around about 01/12/05 05:36, Claude Boucher typed ...
... I usually optimize my
database once a week, removing deleted data with phpMyAdmin.
Any chance you could expand on this?
My box has been in solid use for 9-odd months, but all I do is backup the
SQL [currently every night, with a b
heh heh - its 12 months since my last ext3 reinstall - lost 40gbytes off
an ext3 partition (this being the worst of a number of cases on this
laptop) - I have gone back to resierfs and have been happy since. Too
flaky for me.
I think its a case of YMMV, but I wont be using again ext2/3 except in
Date: Thu, 01 Dec 2005 12:54:44 +0800
From: "W.Kenworthy" <[EMAIL PROTECTED]>
Use LVM.
Yes, I know about LVM, but it doesn't solve my problem, because the
-filesystems- can't be easily resized. (ext3 is easy; it can grow and
shrink. One of JFS or XFS [I can't recall which] can onl
I've been running a Myth system for 9 months now, with programming for
113 channels, 125 videos and 1700 music tracks (for a total of 411,682
records as of now) and I keep it between 35-50 MB. I usually optimize my
database once a week, removing deleted data with phpMyAdmin.
I would say the si
Use LVM.
You can grow/shrink partitions as needed. Just check that the filesystem
used is able to do the same (I use reiserfs with no problems). Also
allows the almost transparent addition of more hard disks if needed. I
will soon be adding around 300G to the mythtv partition (currently part
o
Perfect; that's fairly slow growth. Thanks!
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> guessing that deleting a recording will correctly flush everything
> else associated with it (cutlist, mythcomflagging, etc), but does the
Yes, those get removed.
> DB keep any records of -everything- I've ever recorded, and will those
Yes, an entry goes into oldrecorded with information a
I'm about to repartition, leaving everything except recordings in an
ext3fs partition, and putting all recordings into JFS. But I'd rather
not discover that I've made the ext3 too small, and I'd rather not
waste gigs making it too big.
The only thing I have no idea about is whether the mysql data
28 matches
Mail list logo