Multiple fileserver adds of MDs.

[l3mce]

Replace /usr/pluto/bin/StorageDevices_NFSRadar.sh

http://svn.linuxmce.org/trac.cgi/export/26515/branches/LinuxMCE-1004/src/PlutoStorageDevices/StorageDevices_NFSRadar.sh

This behavior has always existed, but is now exposed by other changes.

[maverick0815]

put the script as prescribed and now everything is quiet on the western front.

[l3mce]

pluto-storage-devices is now updated with this and other changes

[maverick0815]

Like I said...I knew you'd make it :-)
Once in a while I still see a message on my mobile oribter coming up, saying the fileserver has been added, but its by far different from before.
Now, if only mythtv would behave nicely again...but I guess thats not your cup of tea.
I just wanted to say thanks again.

[l3mce]

Setting low expectations of myself rarely leads to failure I guess.

The fileserver adds you get... they are for the MDs? There is some ghost left in the machine. It occasionally causes the core drive to be detected. It occasionally sets a drive offline... and it seems it occasionally re-adds a fileserver. It has something to do with MD connectivity. I will eventually root it out. Any details you might find on those adds would be helpful.

Thanks a lot for your help.

[Armor Gnome]

Thanks to your work on the storage devices radar my videos (stored on a hdd connected to an MD) now shows up on all other MDs.  The only remaining problem is I can not assign metadata or coverart to this media as web-admin>media file sync, can not see that drive.

Eventually I still plan to take that drive out and put it in a NAS but when I do that will I experience the same problem with tags, metadata and accessing the files?  - I also tried other methods such as usb booting that MD and trying to rename all the video files and even destroying the file structure to just dump all media out in the open for lmce to find but nothing has worked.

[maverick0815]

the fileserver adds I see are all refering to the MD. I will check if I can find some additional info in the logs, if that will help.

[maverick0815]

It seems, that the fileserver adds I still see here are related to mythtv....everytime it bombs out and wants to reset the backend, I see at least one of those messages.
The other thing is...I still get messages, that I'm running low on diskspace...

[l3mce]

Are you? df -h

Good work figuring out the mythtical nature of this addition.

[maverick0815]

we talked about this earlier in irc, but see for yourself:

Filesystem            Size  Used Avail Use% Mounted on
rootfs                221G  101G  109G  49% /
none                  1.4G  412K  1.4G   1% /dev
/dev/disk/by-uuid/34072123-4e7d-4b32-bb17-43daad82d54c
                      221G  101G  109G  49% /
none                  1.4G     0  1.4G   0% /dev/shm
none                  1.4G  584K  1.4G   1% /var/run
none                  1.4G     0  1.4G   0% /var/lock
none                  1.4G     0  1.4G   0% /lib/init/rw
/dev/sdb1             1.8T  1.5T  292G  84% /mnt/device/36
/dev/sda3             1.6T  604G  914G  40% /mnt/device/33

[l3mce]

I think it must be warning you about /dev/sdb1  that would likely be your "use this device automatically" drive.

[maverick0815]

hmm...is there a way to customize those warninglevels? I mean...84% on a small drive might be understandable...but on a 1.8TB its a bit much.

[Marie.O]

At the moment DiskSpaceMonitor.sh is configured to alert, if root is 95% full, home is 95% full, or either of them have less than 204800 1k-Blocks free.

[maverick0815]

In that case I should not get ans such message yet, right?

[l3mce]

I am sure this is related to the radar range. Maybe it will reveal a clue as to why it is not understanding which is the install drive, and likely related to the rootfs ident.

Mav... please give me df /  and df /home
Also run this...
bing=$(find /usr/pluto/diskless/ -mindepth 1 -maxdepth 1); bang=$(echo "$bing" | while read i; do echo "$(find ${i}/etc -name 'diskless.conf')"; done); if [[ $(wc -l <<< "$bing") == $(wc -l <<< "$bang") ]]; then echo "Correct"; else echo "Incorrect"; fi

and tell me what it says.