myth version: 0.19.20060121-2

I have /myth/tv mounted to a 1TB smb share (sme server raid5 i-bay). I only want to use about 200MB of the smbfs for myth but it shows 1TB available. How do I keep myth from filling up the smbfs?

I have discovered a setting under utilities/setup/tv settings/general called "extra disk space (in gigabytes)" which looks promising but the highest setting is 200GB, which means that myth would fill up the smbfs to 800GB.

In exporting from raid 5 sme server, is it all or nothing?

It seems far easier to only export the size slice of the array that you want to use than to try to limit usage from myth..

SMe seems to only support smb network shares. There are no options in sme for specifying the size of the export. I dont think sme even natively supports nfs exports due to security reasons.

You should be able to set per user quotas on the SME server. So if you create a user "mythtv" on the SME server, then create a quota for the mythtv user as seen here. This should give you exactly what you want.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1

I wil try that and post my results here.

that worked . . .

mythtv@mythtvbe1:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.0G 2.3G 3.5G 40% /
//betsy/myth-tv 300G 2.3G 298G 1% /myth/tv
mythtv@mythtvbe1:~$

/myth/tv was 900-something G's before.

now if i could just figure out why mythbackend keeps dying. . . . could it have something to do with the /myth/tv mapping in fstab?

It might be worthwhile having a look at your various logfiles under /var/log/, particularly syslog and dmesg. The backend has its own logfile under /var/log/mythtv/ .
It might be worthwhile restarting the backend from a command prompt, this may give you some info when it falls over.

ETA: It might be worthwhile as well having a look at your /var/log/samba/log.mnbd and log.smbd on your MythTV machine and on the SME server.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1

Thanks for aqll your help bruce_s01 - i have created a new topic about the backend issues - it can be found here:

http://mysettopbox.tv/phpBB2/viewtopic. ... 1807#71807

thanks again.

what about limiting the sizer of /myth on a local drive?

I have a 320GB disk (hda) i would like Myth to use about 100GB of

can a similar principle be applied?

I don't know if KM is running with quotas active.
You can resize partitions using qtparted off of one of the bootable Linux distros ((K)ubuntu or Knoppix).
What are you trying to do?

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1

Hi,

Just make the partition a 100 gig. The remaing 220 gig could then be used any way you want as a additional partiton. gparted should resize it for quite nicely
.
Mike

thanks guys will resize it.

I currently have a 100GB /myth in my backend and its ample space for what we record. I want to set my new backend up so that 100GB is used for myth and hte remaining is for storing video / mp3 etc as anoither samba share

please report back in a few months and tell us how far off this quote is...

_________________
R5F1 - Dell P4 2.4Ghz 500MB - PVR250 x 2 - GeForce FX 5200 - Onboard sound/NIC 80GB ATA/250GB ATA/400GB SATA

I have had my current backend running for about 10 months now with a 120GB disk in it.. seriously its fine for what we do. We dont keep stuff, its more a time delay thing. Watch it then delete it.

I am only recording SD digital aswell, I am sure HD would require a whole heap more space