TIP: Click on subject to list as thread! ANSI
echo: rberrypi
to: ROBH
from: MM0FMF
date: 2018-07-10 20:28:00
subject: Re: dev/shm is100%, No sp

On 10/07/2018 17:56, RobH wrote:
> On 10/07/18 15:01, Dennis Lee Bieber wrote:
>> On Tue, 10 Jul 2018 08:53:04 +0100, RobH  declaimed
>> the
>> following:
>>
>>>
>>> pi@raspberrypi:/mnt/CCTV/PiZero $ df -Bm
>>> Filesystem                  1M-blocks  Used Available Use% Mounted on
>>> /dev/root                      14850M 3434M    10752M  25% /
>>> devtmpfs                         182M    0M      182M   0% /dev
>>> tmpfs                            186M  186M        0M 100% /dev/shm <<<<
>>> tmpfs                            186M    8M      178M   4% /run
>>>
>>
>>     There is plenty of space on the SD card -- 10GB of free space.
>> /dev/shm
>> is a RAM disk that is only 186MB total.
>
> If that be the case, I don't know why I was getting the said error message.
>>
>>> Then:
>>>
>>> pi@raspberrypi:/mnt/CCTV/PiZero $ cp /run/shm/*.h264 /mnt/CCTV/PiZero
>>>
>>> Where about 30/40 h264 files were copied across to my NAS /PiZero folder
>>>
>>     Did you examine the time stamps on those files? I'm just curious if
>> they are all recent, or scattered around. Note that rebooting the RPi
>> should result in cleaning out those files too -- should they have been
>> left-overs from development.
>
> The timestamps of the files are 2018-06-24 upto 2018-06-27, and one
> 2018-07-09_22.37.29
>>
>>     And did you examine the NAS to see if copies of those files were
>> on it
>> BEFORE doing the copy?
>
> Yes I did examine the PiZero folder before copying the files across to
> it, and there were no files copied or written while the python script
> was running
>>
>>     If the script is configured as I designed it, it is:
>> 1) capturing to the RAM
>> 2) a few seconds after the capture completes it does a copyfile() to move
>> the captured data to the NAS
>> 3) then does an unlink() of the RAM file, which is supposed to delete it
>> from RAM
>>
>>     If the script is moving files to the NAS, but not deleting them, I'd
>> suspect a problem with the call to unlink(). It is either commented-out
>> (since such was done at one time in the debugging), is somehow not
>> referencing the correct file, or is failing for some reason. If the
>> script
>> is not moving files to the NAS, I'd suspect both the copyfile() and
>> unlink() are commented out.
>>
> The os.unlink line was commented out as I had forgotten to un comment it
> before.
> The script is running now and files are being sent to my NAS drive.
>
> Now here is an interesting thing:
>
> I have just done:
> rob@rob-Z97:~$ cd /mnt/CCTV/PiZero
> bash: cd: /mnt/CCTV/PiZero: No such file or directory
>
> So then:
> rob@rob-Z97:~$ cd /mnt
> rob@rob-Z97:/mnt$ ls
> WinShare
>
> WinShare is a dataset or folder on my NAS drive
>
> I wonder what happened to the mounted PIZero folder, or am I offtrack.
>>
>

Oh good, this thread is back.... I'll fetch my popcorn! :-)

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.