NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
btrfs-cleaner frequently stuck at 100% CPU after 6.4.0 upgrade
Since I upgraded my RN102 to 6.4.0 last night I frequently have trouble reaching the admin interface, and my laptop has reported not being able to reach Time Machine. When I login by ssh and use ...
It seems like I found a way to get rid of the hanging btrfs-cleaner: After switching off quota
btrfs quota disable /data
btrfs-cleaner did never show up again (in top).
(After booting I usualy had about a minute to issue the command before btrfs-cleaner did spawn and prevented the command to respond.)
I did not intentionally enable quota - i guess it was enabled by default.
Good luck,
HansW
PS: Maybe the problem is known by Netgear - in their "FAQs on recently released firmware 6.4.0" (see link on top of page) they talk about "... this is likely due to the ReadyNAS performing a quota check".
Some websites also describe problems with quota and btrfs (Rockstor forum), other sites cite the quota support in btrfs as experimental (but these might be out of date).
I did not extensive testing after diabling quota that way - I'm happy that I can acces my files again ...
Try 6.4.1 beta, it has a fix for your issue.
Well, I'm not to keen on testing Beta-software on my data ...
I uploaded the img-file, rebooted ... and did not look at top :-(
After enbling quota i had a look at top and notticed up to three kworker processes using cpu at 60-90%, with wait at about 5, load netween 1.3 and 3.5.
I just wanted to check, what happens when I disable quota again - wich was not a so-good idea.
since then, the NAS is unreachable again (no ssh, no admin-page).
I'll leave it like that for the moment, hoping it cools down again (not beeing too optimistic).
PS: pings are answered - but I imagine, that's the NIC on its own.
What should have been done was to let the system do what it needs to do to clean things up.
It can take quite some time, especially if volume maintenance hasn't been done.
After rebooting (pulling the cable, power-down-button had no effect) the system welcomed me with "Resyncing started for Volume data".
After that it was quite busy (15-min-load went up to 8.1, kworker using 90% CPU), later it was mainly the processes systemd-journal, md127_resync and md127_raid1. About 6 hours later load was back at 0.3, no process taking more CPU than usual.
The admin page no shows all used space as "data" (no space used by "snapshots", but as there is not much change in the data, the - existing - snapshots may take not much space).
So far: Looks good, thanks Netgear.
What I'd like to know: What was the problem? And which "rare" circumstances led to the complete inaccessibility of the device?
Regards, HansW
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
