>> >I have 650GB on my master backend shared out the sole Myth slave >> >frontend/backend >> >via NFS on which I keep all my recorded shows. A few days ago this filled >> >up. >> >Instead of automaticly deleting older or lower priority shows, as I >> >thought Mythtv >> >was supposed to do, it just continued on recording shows of 0 bytes. > > Just a hunch: although you specify the remaining disk space in > gigabytes, some filesystems reserve a certain percentage of the disk > for root's exclusive use so that logging and daemons would continue to > work if a run-away user process tried to fill the filesystem. From a > user's perspective, "df" would show lots of remaining space (typically > 5% for ext2/ext3) but writing data to files would fail if it resulted > in an allocation request. If that percentage is larger than the fixed > size you specified then the auto-expire routine would never be > triggered. > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing on usenet and in e-mail? > _______________________________________________ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >
This is Reiserfs v3 /w LVM on a hardware RAID 5 array. When I checked with df the whole filesystem was actually used up. So it really IS full and no reserve... The only thing this volume is used for is Myth storage, TV shows, video, music, etc. Programs are on another volume. _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
