kissposa.blogg.se - Ubuntu pcloud

It didn’t take so long until it happened again. It is a harmless warning I would hold off unless it happens again So is any of this a problem for duplicacy? (And even if it were, would it really matter since from the perspective of duplicacy, it is still a local directory and I wouldn’t know how it would know about it also being a samba share, no?) The reason why it is there is because that’s where basically all my free disk space is.

/srv/NAS/ contains a number of directories such as /srv/NAS/christoph that are also made available SMB shares, but /srv/NAS/duplicacy/ is not.

the main storage (a ZFS pool) is mounted as /srv/NAS/ (the NAS directory is really not needed, it could just as well be directly in /srv but I wasn’t sure whether /srv is used for anything else so I added another level, just to be sure).

I don’t know linux so well, but I don’t think this is a samba mount. It looks like a samba mount so it must be samba that opened too many files at a time when there were many chunks to be saved to the local cache.

So what does this tell me? Doesn’t look like the CLI has an awful lot of files open… Lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfsĬOMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEĭuplicacy 20503 root cwd DIR 0,49 3 389369 /srv/NAS/duplicacy/duplicacy-web/repositories/localhost/allĭuplicacy 20503 root rtd DIR 8,2 4096 2 /ĭuplicacy 20503 root txt REG 8,2 26806950 524332 /.duplicacy-web/bin/duplicacy_linux_圆4_2.3.0ĭuplicacy 20503 root 0r CHR 1,3 0t0 6 /dev/nullĭuplicacy 20503 root 2w CHR 1,3 0t0 6 /dev/nullĭuplicacy 20503 root 3u sock 0,0865 protocol: TCPĭuplicacy 20503 root 4u a_inode 0,13 0 10602 ĭuplicacy 20503 root 5u sock 0,0870 protocol: TCPĭuplicacy 20503 root 6u IPv4 40321058 0t0 TCP server:38002->:https (ESTABLISHED) Then run lsof -p which will show files opened by the CLI. Whose fault is this? (I’m not meaning to blame anyone but trying to understand what’s going on.) I’m inclined to believe that this is at least also a problem of duplicacy. I’m somewhat puzzled why I’m running against any limit here. So does this mean that I’m not running against the system limit of open files but against the max of 4096 open files that duplicacy is allowed? Max realtime timeout unlimited unlimited us

Max address space unlimited unlimited bytes Max resident set unlimited unlimited bytes Probably it doesn’t matter for this purpose, so I tried the first one: $ cat /proc/31618/limits