Suspected *BUG* with Omada APP (Android?) - Most Active Clients
Not sure if this is the Android application or the Linux Controller, but I came across a fun one the other day. I think somebody skipped the 'T' in the KMGTP sequence.
I am replacing my 10-year old Synology NAS with a new one, and I've transferred quite a lot of data from the old one (just under 4TB), but the Omada Android client is showing the new NAS as having used 3.6PB (yes, PETA-bytes). For those that are about to Google it, each PB is 1,000,000 GB or 1,000 TB.
Here's where the math gets fun. I only powered up my shiny new NAS for the first time almost 15 days ago, and it is connected to my Omada switch via a GbE (1Gbps port).
15 days X
24 hours X
3,600 secs/hour X
1,000,000,000 bps
Divide that by 8 to get bytes
Divide that by 1,048,576 to get MB
Divide that by 1,048,576 to get TB
You get: 147.3TB
it's not even physically possible for my NAS to have done the following, even if the port was PINNED 24/7 at 1Gbps for two weeks (it would need almost a year!):
and here's the client (Synology NAS) history breakdown from the app.
As you can see it manages about ~5TB/day between the two boxes.