[mythtv-users] Odd: Storage Group is showing two different drives as the same MythTV drive

[Michael T. Dean]

On 07/25/2007 12:38 PM, Robert Kulagowski wrote:
>      * MythTV Drive #2:
>            o Directories: mbe:/mnt/d3/video, mbe:/mnt/d4/video
>            o Total Space: 305,122 MB
>            o Space Used: 104,125 MB
>            o Space Free: 200,997 MB
>   
...
> $ df
> /dev/sda6            310333324 110571892 199761432  36% /mnt/d6
> /dev/sdb1            312445808 190638236 121807572  62% /mnt/d1
> /dev/sdc1            312445808 112946616 199499192  37% /mnt/d2
> /dev/sdd1            312445808 105659152 206786656  34% /mnt/d3
> /dev/sde1            312445808 106638676 205807132  35% /mnt/d4
> /dev/sdf1            390567516 288744124 101823392  74% /mnt/d5

Partitions /dev/sd{b,c,d,e}1 all have the exact same size and /dev/sdd1
and /dev/sde1 have free space that is within 5 seconds of your max
recording bitrate, so...

dd if=/dev/zero of=/mnt/d4/delete_me bs=1M count=100

should make this "temporary" mistake disappear (for now :).  Or, with
the appropriate of, bs, and count, you could make all of the disks
appear as the same one in your status report.  (BTW, just guessing a
value for count--may need to increase it.)

See  BackendQueryDiskSpace() in programs/mythbackend/backendutil.cpp
around line 179.  AIUI, the issue is there's no good (and
platform-independent) way to identify whether two directories are on the
same filesystem--especially with network mounts involved--so Myth has a
"pretty good" approach.  Chris Pinkham will have to answer whether this
affects reporting only or also affects recording-location decision
making.  But, still, it would be an ephemeral condition that would be
rectified by just one recording to either drive, so, IMHO, isn't a big
worry even if it does affect recording.

However, I do have a question.  Every once in a while in your master
backend log, you should see, "AutoExpire: Found max recording rate of
XXX MB/min".  What's the value you get?

Thanks,
Mike