On a fresh install of mythtv onto a 10 gig drive (I'm not using a TV card, so no need for big storage), it partitioned the drive into 4 parts, like it should.

I didn't notice any problems at first, since I'm remote mounting network shares for my videos, music, etc... but when I went to put mame roms directly into /myth/games/xmame/roms (which is in the /myth mounted partition) it ran out of space WAY too early. I was putting in about 600 megs of data, and the disk free (df -h) claimed that 4 gigs of space were on the partition. But it failed to do even 400 megs... started getting DISK FULL type errors.

Tried to put data into the /cache directory/partition also, and ran into the same problem: the space free doesn't match what it claims the size is.

Is something screwy with the autopartitioning of knoppmyth? Is it fscking the partitions correctly? Looks like it's not.

Help?

(In the meantime, I'm just continuing to remote mount directories as I need them... so now my roms are on another box, but I'll really like to put them right onto the mythbox.

Seth

Try this :

df -i

Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda1 262144 21702 240442 9% /


and check the column Iuse %

If your partition if full of inode, you need to reformat it with different settings for the clusters size.

Good luck

Yhan

Yes, that's exactly the problem...

df -h:
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 2.0G 1.6G 317M 83% /
/dev/root.old 2.2M 342K 1.8M 16% /initrd
/dev/hda3 3.1G 40K 3.1G 1% /cache
/dev/hda4 4.0G 35M 4.0G 1% /myth

df -h
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda1 208384 66915 141469 33% /
/dev/root.old 2504 434 2070 18% /initrd
/dev/hda3 800 13 787 2% /cache
/dev/hda4 1024 46 978 5% /myth

This was autodone from KnoppMyth.... weird... why did it use such low inode values????

Actually I got the same problem on my /myth partition.

I think they do in that way (cesman correct me if I'm wrong) to optmize the reading speed.

As the majority of the files on that partition, for the tv recording are very large, you can gain some speed if you format it with large clusters.

if you want to correct that, you need to reformat.

Yhan

this is a problem with the ext3 filesystem. Since romfiles are very small, and you are likely to be using thousands of them if you have a large collection, I suggest you do as I have and reformat your /myth partitions as reiserfs.

not that going to reiserfs or xfs is bad, but just want to point out that it is not a problem or limitation of the ext3 filesystem. The issue arrises, because of the way the partition was formated, which was done intentionally, if you reformat with the default settings for ext3 the problem will go away just like it does moving to a different filesystem.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets