File system running out of Inodes

Status
Not open for further replies.

Wilbertcr

Dabbler
Joined
Nov 8, 2013
Messages
13
It seems something is happening with btsync. Following the errors the console is showing me:

Nov 10 10:44:21 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125060 on /mnt/Drive500: out of inodes
Nov 10 10:54:21 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125060 on /mnt/Drive500: out of inodes
Nov 10 10:58:07 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Nov 10 10:58:12 freenas last message repeated 2 times
Nov 10 11:04:21 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125060 on /mnt/Drive500: out of inodes
Nov 10 11:11:29 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:12:01 freenas last message repeated 22 times
Nov 10 11:14:02 freenas last message repeated 62 times
Nov 10 11:14:11 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:14:21 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125060 on /mnt/Drive500: out of inodes
Nov 10 11:14:21 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:15:02 freenas last message repeated 4 times
Nov 10 11:17:01 freenas last message repeated 12 times
Nov 10 11:17:03 freenas kernel: pid 10109 (smbd), uid 65534 inumber 2 on /mnt/Sata: out of inodes
Nov 10 11:17:03 freenas smbd[10109]: unknown tag type 64
Nov 10 11:17:12 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:17:52 freenas last message repeated 4 times
Nov 10 11:18:00 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:00 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Nov 10 11:18:01 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:02 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Nov 10 11:18:03 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:06 freenas last message repeated 2 times
Nov 10 11:18:06 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Nov 10 11:18:07 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:39 freenas last message repeated 21 times
Nov 10 11:18:45 freenas last message repeated 4 times
Nov 10 11:18:46 freenas kernel: ufs_accessx(): Error retrieving ACL on object (6).
Nov 10 11:18:47 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:49 freenas kernel: ufs_accessx(): Error retrieving ACL on object (6).
Nov 10 11:18:49 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full
Nov 10 11:18:59 freenas last message repeated 6 times
Nov 10 11:19:00 freenas kernel: ufs_accessx(): Error retrieving ACL on object (6).
Nov 10 11:19:00 freenas kernel: pid 2626 (btsync), uid 0 inumber 14125061 on /mnt/Drive500: filesystem full

I restart fixed the problem but it seems this is building up pretty quickly, since the last restart took place just about 8 hours before this problem started.

Thanks!
 

Wilbertcr

Dabbler
Joined
Nov 8, 2013
Messages
13
BTW, btsync is running from the /mnt/Drive500/sync/btsync, is that the problem? Should it be running from the system drive?
 
D

dlavigne

Guest
What is the layout of your disks? e.g. filesystem and type of RAID, if used
 
Status
Not open for further replies.
Top