==> Changing ownership on every restart
-
Hi,
in my Cloudron use case, I backup a Cloudron instance with 41 apps (as crypted tgz files) to a different Cloudron instance with the minio app. I've observed in case of minio updates, that this special minio app needs up to 4 hours to get back beeing responsive. Can we put the chown command into a kind of "hot fix" instead of using it on every restart?
Do others have the same issue? -
I am surprised as well. chown should be quick enough (not 4 hours anyway). Do you get the same performance if you run the command on the server directly? How much data are we talking about (you can do
find . -type f | wc -l
in the data directory ) ? -
sorry for "lying". it felt like 4 hours. the last update/restart takes only 1h10m
Sep 11 17:08:53 ==> Changing ownership
Sep 11 18:16:21 ==> Starting minio:/app/data#find . -type f | wc -l
50 minutes later
1178082 -
OK, I have pushed an update now which will chown only if required. It's a bit of hack, but if it causes problems we can fix it in a future update.
-
I've run the update. It's a little bit faster:
Sep 11 21:58:16 ==> Changing ownership
Sep 11 22:41:17 ==> Starting minio -
strange, I use a Minio app on Cloudron with about 300GB files (backup from my MacBook) and there are absolutely no issues, after update it's immediate available
-
@luckow Oh, let me guess maybe it's on a filesystem which is not ext4 and does not actually support permissions! can you do
ls -l /app/data
? -
@girish said in ==> Changing ownership on every restart:
ls -l /app/data
from inside the container it looks like
root@3435b3d0-07cb-4c5e-9723-d69d7feb6285:/app/code# ls -l /app/data
total 4
drwxr-xr-x 4 cloudron cloudron 4096 Sep 11 20:41 data -
-
taken from https://my.example.org/#/system
/dev/sda4 mounted at /home
This ext4 disk contains: ...