[mythtv-users] Re-doing my backend

David Frascone frasconebulk at gmail.com
Fri Feb 8 04:53:33 UTC 2008


On Feb 7, 2008 4:28 PM, R. G. Newbury <newbury at mandamus.org> wrote:

>
> The better solution, IMHO, is small disk for the OS with at least 2
> partitions, and rsyncing the important data to the the big video disk
> every night with cron. The OS disk partitions include one for '/', one
> for /home (which stores copies of important stuff from /etc too) and
> possibly one for /var (so that /var/lib/mysql is not on the OS
> partition). Revising /etc/my.cnf can put mysql at /home/msyql, hitting 2
> birds with one stone. (This is for Fedora)
>
> Note that if your log files (in /var) fill the partition, then Fedora
> (linux generally?) may crash and will not re-boot. If running myth you
> may suddenly find that there are no programs displayed in 'Watch
> Recordings' (since mysql cannot now write to
> /var/lib/mysql/mythconverg). All is not lost however!
>
> Note that the OS and /home etc will easily fit in 12 or 13 G harddrive,
> IF you can find one!
>

Why rsync over a raid1?

And, how can I raid 1 two distinct partitions on two distinct disks . . .
smells like lvm.

As far as disk filling goes, I fix that with my frontends by loop-back
mounting their root filesystems.  So, They have 10Gb or so "disks" that I
loopback mount, and *then* nfs export, so that if they go crazy log-wise,
they only kill themselves.

This will be harder with the backend being the server -- I may put /var into
it's own partition . . .

-Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080207/d1cb6dcd/attachment.htm 


More information about the mythtv-users mailing list