ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | Armbian 20.11 Tamandua released | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
Net147 has quit [Quit: Quit]
Net147 has joined #armbian
Net147 has quit [Remote host closed the connection]
Net147 has joined #armbian
Net147 has quit [Remote host closed the connection]
<lanefu> stipa: what are you crunching with opencv
Glock24 has joined #armbian
loredin has quit [Ping timeout: 265 seconds]
loredin has joined #armbian
torv_ has quit [Ping timeout: 268 seconds]
torv_ has joined #armbian
Glock24 has quit [Remote host closed the connection]
<stipa> lanefu: it's deletes a post on linkedin every 30 minutes and posts it again, the same one
<stipa> something like an advert
<stipa> instead of me wasting time there trying to be at the top of the feed i did a python script to do it 48 times a day
<stipa> i tried other stuff like with headless chromium but that didn't work since they somehow change the code of the linkedin or something so scrapers can't work anymore
<stipa> but computer vision works ok
<stipa> since it behaves like a human
<stipa> very primitive AI
<stipa> but, headless chrome and some other stuff would waste less resources and they could run from the CLI environemnt, but what can you do...
<stipa> adapt or die
<stipa> i had a problem with linkedin, script was clicking to fast
<stipa> their system noticed and i was baned
<stipa> they returned me account but i had to slow the vision a little bit
<stipa> their system noticed that it doesn't behave like a human since it clicks and moves mouse like super fast machine
<stipa> i guess
<stipa> since i slowed it down they're not complaining
<stipa> but they also don't know why i was banned since their systems are "Automated"
<stipa> go figure
<stipa> i was lucky
grae has joined #armbian
grae_was_taken has joined #armbian
grae has quit [Ping timeout: 258 seconds]
<lanefu> Lol
<lanefu> Wow
<stipa> yeah
<grae_was_taken> huh
* Tony_mac32 reclaiming workbench, only crying a little about throwing things away
<Tony_mac32> don't even bother asking why there's a mason jat next to the oscilloscope
<Tony_mac32> jar*
<stipa> i don't like to throw things either, after some time i need to buy them...
<stipa> like, i threw that 5 years ago, idiot
<stipa> now i have to buy it
<stipa> things are great for hasking stuff
<stipa> hacking*
<stipa> like, materials
<stipa> that can't be made at home
<stipa> like ,piece of flat piece of plastic from some packaging or something, but it costs money if you want to buy it and need it atm
<stipa> even going to shop costs money...
<stipa> but, then, there is limited amount of space...
<Tony_mac32> haha
<stipa> harsh reality
grae_was_taken has quit [Quit: Leaving]
kcz has quit [Remote host closed the connection]
kcz has joined #armbian
ChriChri_ has joined #armbian
ChriChri has quit [Ping timeout: 246 seconds]
ChriChri_ is now known as ChriChri
<ArmbianTwitter> @kobol_io (Kobol Innovations): @gnomethrower The thread is not locked and we replied to it. Armbian forum policy for new user limits to one message per day until you gets a like (this is to avoid spam bot). We gave you a like so the limitation should be removed soon. https://tinyurl.com/y28gvtvf (9s ago)
macc24 has joined #armbian
chiui has joined #armbian
<IgorPec> good morning
peterm6881 has joined #armbian
archetech has quit [Quit: Leaving]
peterm6881 has quit [Remote host closed the connection]
<ArmbianTwitter> @Poddingue (Bruno Verachten 🍰): I will give a talk on behalf of @WorldlineGlobal at @fosdem 2021 on Sunday. Feel free to join if you want to learn more about #gitlabci on #Arm #SBC, #Armbian and #HypriotOS. 🍌🍊🍍 https://t.co/20TfFsgDqS https://tinyurl.com/yyq8vjxf (5s ago)
plntyk has joined #armbian
manpaz has quit [Remote host closed the connection]
<ArmbianTwitter> @armbian (armbian): RT @Poddingue: I will give a talk on behalf of @WorldlineGlobal at @fosdem 2021 on Sunday. Feel free to join if you want to learn more abo… https://tinyurl.com/y4r7x2df https://tinyurl.com/y62mnt6c (1s ago)
archetech has joined #armbian
nkuttler has quit [Quit: K-Lined]
nkuttler has joined #armbian
scope has joined #armbian
The-going has joined #armbian
axledwarf has joined #armbian
axledwarf has quit [Remote host closed the connection]
Net147 has joined #armbian
macc24 has quit [Ping timeout: 264 seconds]
macc24 has joined #armbian
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #armbian
macc24 has quit [Ping timeout: 240 seconds]
Redentor has joined #armbian
macc24 has joined #armbian
Redentor has quit [Remote host closed the connection]
macc24 has quit [Ping timeout: 256 seconds]
chrisd has joined #armbian
<chrisd> I think I've found a bug in armbian-resize-filesystem
<chrisd> Wondering how to report it.
<IgorPec> shoot
* [TheBug] *BANG*
<IgorPec> not you :)
<chrisd> line 56 is supposed to align to 16MiB sizes
<chrisd> but I think it's aligning to 16KiB sizes
<Xogium> [TheBug]: damn it ! I told you just how many times to put a silencer on that damned thing ?
<Xogium> ;)
<[TheBug]> :D
<chrisd> The 32 should be 32768
<chrisd> and later in the line the 3200 should be 376800
<IgorPec> idk, didn't create this part
<IgorPec> trying to understand why this is wrong or was it correct once but its wrong now
<IgorPec> aha, i see this is only used if RESIZE_VALUE is defined
<IgorPec> which normally is not
<IgorPec> best is if you just prepare a patch with comment
<chrisd> OK. Have not done this for a long time :)
<chrisd> One of the hurdles was just finding where to report it
<chrisd> your link helped, thanks
<IgorPec> fork project, file location is above, create a pull request
<chrisd> thanks, bye
chrisd has quit [Quit: leaving]
manpaz has joined #armbian
<Church-> Hmm anyone have a guide on tuning nfs on armbian? Seeing some high load average with low CPU usage
<IgorPec> armbian runs with lets say 20 different hw interfaces (kernels) on hundreds of different hw configurations.
<IgorPec> on hw level we apply certain optimisations which should make some difference
macc24 has joined #armbian
<IgorPec> while on the NFS protocol level, this is probably a question for NFS gurus
<Church-> Nod got it
<IgorPec> on which hw do you do this?
macc24 has quit [Ping timeout: 272 seconds]
<Church-> IgorPec: Helios64
<Church-> So let me get the chip
<Church-> rockchip64/RK3399 hexa-core soc
<[TheBug]> I mean, what are you seeing / expecting
<[TheBug]> even if bound to one CPU, which it's not, you should be able to max gigabit network no issue?
<IgorPec> which board specifically?
<[TheBug]> I use NFS w/ mdadm raid5 on rk3399 (RockPi 4c) and not see any issue
<[TheBug]> you are using ZFS if I recall
<[TheBug]> so, maybe overhead from that is the issue
<Church-> Ah so I guess it's mostly precationary? Getting a 100% load average message from motd on ssh in. Load average is only 6.30~ from an upper bound. Haven't profiled what's out of turn for this box yet.
<Church-> Haven't noticed any degredations however
<[TheBug]> thats wait
<[TheBug]> check top when you see this
<[TheBug]> look in the section for io wait
<[TheBug]> this will probably be like 20-30%
<[TheBug]> your system has high load because it is having IO wait some
<Church-> avg-cpu: %user %nice %system %iowait %steal %idle
<Church-> 1.80 0.00 2.48 5.70 0.00 90.02
<[TheBug]> the load is artificial to actual CPU usage
<Church-> From iostat
<Church-> Yep it is
<Church-> I figured it was IO bound
<Church-> Given actual CPU usage was almost non-existent
<[TheBug]> its supposed to give you an idea that things are being queued and that if you try now with a hard load, you may have wait .. so load is showing it believes current rate of work its backed-up a bit there, but if its still responsive/ doing what you expect, then this is expected
<Church-> Okay got it. Thanks!
<Church-> Just wasn't sure, first using a NAS and zfs that wasn't just a HDD attached to my htpc
<Church-> first time*
<[TheBug]> hehe yeah.. also if you are newer to linux another fun gotcha is ram and how it is used can be confusing sometimes
<IgorPec> yeah, ZFS can certainly add some troubles here
<[TheBug]> https://www.linuxatemyram.com/ if you have any confusion there is a great resource :)
<IgorPec> but am not paying much attention to zfs issues
<Church-> [TheBug]: Yeah my most recent manager gave me a great breakdown on RES/VIRT one day heh
<Church-> Yeah I assume most of the issue is the SMR drives. Will probably slowly replace them as they fail/get close to failing
<Church-> Although reads should be mostly fine there
<[TheBug]> honestly the biggest issue in that case would be the drive not waking fast enough, you don't really have enough drives / probably not active enough to really cause issue from SMR specifically
<[TheBug]> most people whom have that issue are in production where they are pushing the drives and the hardware arrays have a specific expectation of what the drive will do in a specific time, and if it doesn't results in errors
<[TheBug]> I don't think you should really see that issue in a 5? drive array like you are trying
<Church-> Yeah it's just 5 drives in a raidz2, a single application (jellyfin) using it with almost no writes except in heavy bursts once every two weeks to add more media
<[TheBug]> I have a setup where I have an 8 port raid card and then attached a drive via USB 3.0 to sata UAS and its a 9 drive raid.. and I can say the use of USB in that case can make a delay cause USB likes to power down the one drive -- I think that issue I have would more likely cause some issue / failure than you using SMR drives in array like you are.
<[TheBug]> s/8 port raid/8 port sata
<ArmbianHelper> [TheBug] meant to say: I have a setup where I have an 8 port sata card and then attached a drive via USB 3.0 to sata UAS and its a 9 drive raid.. and I can say the use of USB in that case can make a delay cause USB likes to power down the one drive -- I think that issue I have would more likely cause some issue / failure than you using SMR drives in array like you are.
<[TheBug]> so far it's been okay, just some delay if requests haven't been made to it in a while
<Church-> Eesh yeah that delay could cause some fun issues
<[TheBug]> but sometimes you will see usb reset in dmesg for example, which isn't good really in a raid.. its a testing setup to see what I could do...hehe
<[TheBug]> bunch of old 2TB's
<Church-> Heheheh neat
peterm6881 has joined #armbian
peterm6881 has quit [Remote host closed the connection]
macc24 has joined #armbian
macc24 has quit [Ping timeout: 258 seconds]
The-going has quit [Remote host closed the connection]
<stipa> [TheBug]: have you tried blacklisting usb devices from going to autosuspend with TLP ?
archetech has quit [Quit: Leaving]
archetech has joined #armbian
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
raver has joined #armbian
Elpaulo has joined #armbian
s_frit has quit [Remote host closed the connection]
s_frit has joined #armbian
archetech has quit [Quit: Leaving]
chiui has quit [Ping timeout: 260 seconds]
archetech has joined #armbian
oida has quit [Quit: byez]
oida has joined #armbian
raver has quit [Quit: Gateway shutdown]
archetech has quit [Remote host closed the connection]
raver has joined #armbian
raver has quit [Client Quit]
raver has joined #armbian
raver has quit [Client Quit]
raver has joined #armbian
raver has quit [Client Quit]
raver has joined #armbian
raver has quit [Quit: Gateway shutdown]
archetech has joined #armbian
raver has joined #armbian
grae has joined #armbian
grae has quit [Remote host closed the connection]
raver has quit [Quit: Gateway shutdown]
raver has joined #armbian
scope has quit [Ping timeout: 260 seconds]
torv_ has quit [Ping timeout: 268 seconds]
torv_ has joined #armbian
macc24 has joined #armbian
raver has quit [Quit: Gateway shutdown]
raver has joined #armbian
raver has quit [Client Quit]
raver has joined #armbian