Total DISK READ :       0.00 B/s | Total DISK WRITE :       0.00 B/s
Actual DISK READ:       0.00 B/s | Actual DISK WRITE:       0.00 B/s
  PID  PRIO  USER     DISK READ  DISK WRITE  SWAPIN     IO>    COMMAND
   87 be/3 root          0.00 B    136.00 K  0.00 %  0.03 % 
[jbd2/mmcblk0p2-]
14302 be/4 root          0.00 B    704.00 K  0.00 %  0.00 % python 
/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
12435 be/4 pi            0.00 B     24.00 K  0.00 %  0.00 % vmstat 60 1440
  495 be/4 root          0.00 B     16.00 K  0.00 %  0.00 % rsyslogd -n


On Tuesday, November 1, 2016 at 9:28:58 AM UTC+1, Glenn McKechnie wrote:
>
> run iotop as * iotop -oaP * This will show running process's only and 
> accumulated totals - run it for a while and you'll get a better feel of 
> what's happening as regards total writes.
>
> sqlite write total will be included under the python /usr/bin/weewx total 
> - sqlite is a friendlier option for the SDCard
>
> /dev/ttyUSB0 should be dealt with in memory, no disk access involved
>
> logging will be visible under iotop as rsyslogd -n (or whatever daemon you 
> use).  Turns out, it's not as big a burden as it's made out to be; at least 
> on the systems here.
>
> I wouldn't have thought ftp would add any burden - the files have been 
> generated already and it's just reading them.
>
> As you say, it is a bit odd.
>
>
> Cheers
>  Glenn
>
> rorpi - read only raspberry pi + weewx: now with scripts 
> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>
> On 1 November 2016 at 18:52, Jacek Skowroński <[email protected] 
> <javascript:>> wrote:
>
>> iotop shows nothing special from time to time 50KB/S write but total is 
>> always 0.
>>
>> I use sqlite version - and the file weewx.sdb was located on external USB 
>> Flash
>>
>> I have default skin, I send data to 4 weathers services and ftping those 
>> to my web server - located in external DC.
>>
>> So in my point of view it's crazy!!!
>>
>> One of my friend told me that the problem could be reading data from 
>> /dev/ttyUSB0 and putting logs on sd card
>>
>> W dniu 2016-11-01 o 00:53, Glenn McKechnie pisze:
>>
>> One way to lock up your SDCard is outlined at rorpi - read only 
>> raspberry pi + weewx: now with scripts
>> <https://github.com/glennmckechnie/rorpi-raspberrypi> 
>> Making the / filesystem 100% read-only should go some way to ensuring the 
>> SDCard will stay around longer. While it mentions using USB sticks and hdd 
>> drives as writable alternatives, the responses in this thread regarding 
>> those will be more useful to you. (FWIW, I find the RAID 1 USB stick setup 
>> intriguing!)
>>
>> Interesting that you've lost so many cards, and have eliminated your 
>> power supply as a problem.
>> How busy is your system? If you run iotop (apt-get install iotop) what 
>> does it show? 
>> <https://github.com/glennmckechnie/rorpi-raspberrypi/wiki/rorpi-raspberrypi-preinstall#Disk_access_viewing_with_iotop_oaP>
>>
>> Are you using mysql? It's a lot busier when it comes to disk access.
>> Also, are you only generating the one skin on the pi? If you have 
>> multiple skins (testing them out or whatever) the image files tend to add 
>> up ( I bricked an 8gb Sandisk Cruzer doing this ), especially at archive 
>> intervals less than 5 minutes. 
>>
>> Cheers
>>  Glenn
>>
>> rorpi - read only raspberry pi + weewx: now with scripts 
>> <https://github.com/glennmckechnie/rorpi-raspberrypi>
>>
>> On 31 October 2016 at 19:34, Jacek Skowroński <[email protected] 
>> <javascript:>> wrote:
>>
>>> Hi, 
>>> How does Your sd card "live" in raspberry pi?
>>> On my example I lost 5 cards already - all of them by 3-4months long.
>>> Is it normal?
>>>
>>> Yust now I'm looking to get rid of sd cards and write down data 
>>> somewhere else.
>>> Any topics? Any hints?
>>>
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/atRpRzKrlyk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to