19.12.2018, 11:02 (This post was last modified: 19.12.2018, 11:03 by davidsilva.)
Hi I have a LM5Lp2 but all changes that I try to do, disappear.
In bottom bar appear one more information: Disk: 100% which usually doesn’t appear. If I try to export to another Logic Machine this information doesn’t appear.
When I go to the menu System config -> Status -> System status -> Partitions, the file system “/dev/mtdblock0” is full.
Why it’s happen?
How many trends do you have? /dev/mtdblock0 stores databases and trends. You will probably have to delete some trends to free up space for the main database.
19.12.2018, 11:45 (This post was last modified: 19.12.2018, 11:47 by davidsilva.)
(19.12.2018, 11:16)Daniel. Wrote: Hi
Try updating FW to RC1
BR
Hi,
This is the Version 20180822. Isn’t it the last?
Best regards,
(19.12.2018, 11:19)admin Wrote: How many trends do you have? /dev/mtdblock0 stores databases and trends. You will probably have to delete some trends to free up space for the main database.
Hi,
I only have 7 trends. On previous projects I used more and had no problems.
(19.12.2018, 11:54)Daniel. Wrote: You probably used lower resolution. Change from 5years to 2 and you will shrink it by 3. Latest FW is RC1 20180828
Hi,
I update the FW, delete 5 trends, change the resolution from 5 years to 2, and the disk kept at 100%. After waiting 10 min, I rebooted the LM and the trends appeared again without changes.
Hi
The device with splitted drive for data is available max for 2 years. So there coulnd't be older data than two years. 12*24*365*2=210240. 4136KB/210240 = 20B per one trend row. It's 2x more than I would expected for storing decimals with zero precision. Isn't it a bug?
LM5Lp, firmware: 2018.08.22 and 2021.12.15, FlashSYS v2, ARMv7 Processor rev 5 (v7l), kernel 4.4.151 and 4.4.259
(19.12.2018, 12:53)Thomas Wrote: Hi
The device with splitted drive for data is available max for 2 years. So there coulnd't be older data than two years. 12*24*365*2=210240. 4136KB/210240 = 20B per one trend row. It's 2x more than I would expected for storing decimals with zero precision. Isn't it a bug?
When you create a trend LM reserve already final size for this trend. Even empty trend once created will have final size. Otherwise we will have constant memory problems or disk size.