[tar -C fails]

as a software dev myself (with not a lot of filesystem knowledge) I just ask myself why they wrote this awesome filesystem if it doesn't work like a filesystem? kinda destroys the purpose in my opinion, but this might be a special case and only my opinion

[tar -C fails]

Just looked at the command you're running, if it's all in your appdata share, then that should be cache only, so why can't you use /mnt/cache/ instead of /mnt/user/ ?

My appdata is not cacheonly, which is not best-practice as it seems. I also have jira running on it and don't want to have all the files uploaded there on the cache (which may be worked around by adding an extra -v for the data in jira)

[tar -C fails]

not so big, only 15GB, it just feels like a step backwards if I move it to a disc and not a share.. specially since other apps also use that disk which may fill it up

[tar -C fails]

so, there is no way for me to scale gitlab over more then 1 disk?

 

This sounds pretty major to me, sucks if the devs really won't work on this

[tar -C fails]

which links? Can you point me to some docs or post?

is this unraid related or docker?

[Postgres and filesystem rights]

bumping this up, since it isn't fixed yet and I have another filesystem problem in /mnt/user now and these may be related?

http://lime-technology.com/forum/index.php?topic=49736.0

[tar -C fails]

tar -xf /mnt/user/appdata/gitlab/backups/repositories/xxx/xxx.bundle -C /mnt/user/appdata/gitlab/repositories/xxx/xxx.git

tar: ./hooks: Cannot utime: No such file or directory

tar: Exiting with failure status due to previous errors

 

works if I user disk1 or disk2 as a target, can't restore gitlab backup because of this. Using latest stable release

Anyone had this issue and knows workarounds / when this will be fixed?

 

[SOLVED - Getting Out of Space Message while copying to array, but I have space.]

Is your cache disk full by chance?

doesn't unraid handle this on its own??

[Postgres and filesystem rights]

I fixed it by running it on a cache-only share and using /mnt/cache/pgdata. But that's just a workaround

[Postgres and filesystem rights]

Hi,

I have a problem running the official postgres docker image with PGDATA set.

 

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -it --name="Postgres" --net="bridge" --privileged="true" -e POSTGRES_PASSWORD="pw" -e PGDATA="/data" -e TZ="America/Los_Angeles" -p 5432:5432/tcp -v "/mnt/user/appdata/pgdata/":"/data":rw postgres:9.4

 

Output:

root@Appserver:~# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -it --name="Postgres" --net="bridge" --privileged="true" -e POSTGRES_PASSWORD="pw" -e PGDATA="/data" -e TZ="America/Los_Angeles" -p 5432:5432/tcp -v "/mnt/user/appdata/pgdata/":"/data":rw postgres:9.4

The files belonging to this database system will be owned by user "postgres".

This user must also own the server process.

 

The database cluster will be initialized with locale "en_US.utf8".

The default database encoding has accordingly been set to "UTF8".

The default text search configuration will be set to "english".

 

Data page checksums are disabled.

 

fixing permissions on existing directory /data ... ok

creating subdirectories ... ok

selecting default max_connections ... 100

selecting default shared_buffers ... 128MB

selecting dynamic shared memory implementation ... posix

creating configuration files ... ok

creating template1 database in /data/base/1 ... LOG:  could not link file "pg_xlog/xlogtemp.23" to "pg_xlog/000000010000000000000001": Function not implemented

FATAL:  could not open file "pg_xlog/000000010000000000000001": No such file or directory

child process exited with exit code 1

initdb: removing contents of data directory "/data"

 

Someone can help me with this? It's working without PGDATA, but that's not an option for me since I need persistence storage tested it with 9.4 and latest, both are not working

[White webgui after Plugin install]

Deleting the *.pkg did it, thanks!

[White webgui after Plugin install]

Hi,

just started using unraid, setuped some docker containers and then installed this plugin: https://raw.githubusercontent.com/Influencer/UNplugged/master/headphones_unplugged.plg

 

The plugin is old and not supported anymore as it seems (I didn't check that before installing it). Now the webgui is only a white page with no content (But returning a HTTP 200), docker container are still running.

After restarting the server the docker containers are not running and the webgui is still returning a blank page with HTTP 200

 

Anyone can help me with this? Or will I have to reinstall everything?

 

EDIT:

just found out that plugins/packages are installed on the flash drive, is removing the responsible plugin folder / packages enough? Can I remove the python package safely if I have not installed any other Plugins?