[solved] cache disk size wrong


Recommended Posts

hi

 

unraid 6.5.3 pro

 

since few days i got notifications that indicate my cache disk is full...this is totally wrong

 

/dev/sde1       448G  152G  295G  35% /mnt/cache

 

 du -h -d 1 /mnt/cache
101G    /mnt/cache/system
17G     /mnt/cache/appdata
26G     /mnt/cache/domains
144G    /mnt/cache

 

Why i got this error and notification ?

Edited by ibasaw
Link to comment

Probably not related but there's a lot of

Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Failed terminating the transaction
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

in your syslog. I don't know how serious that is but it would be worth investigating.

Link to comment
On 8/24/2018 at 2:51 PM, John_M said:

Probably not related but there's a lot of


Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Transaction timeout
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: Failed terminating the transaction
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Aug 18 14:10:32 THE-BEAST kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

in your syslog. I don't know how serious that is but it would be worth investigating.

seem to be related to ipmi sensors

Edited by ibasaw
Link to comment
  • 2 weeks later...

Not obviously related, but I notice you have a very large docker image of 100G. This is often a sign that a user has had problems with docker image filling up due to misconfigured dockers and they try to fix it by increasing size of docker image. Most people never need more than 20G docker image when their dockers are configured correctly.

Link to comment
Not obviously related, but I notice you have a very large docker image of 100G. This is often a sign that a user has had problems with docker image filling up due to misconfigured dockers and they try to fix it by increasing size of docker image. Most people never need more than 20G docker image when their dockers are configured correctly.
My is 100Gb cause I may it 100GB why? I have a 2TB cache, repourposed drive from the array.

Anyhow I had this problem once, webgui kept telling me I had 135gb free on a 250gb SSD. One day everything came to a gridding halt. The cache shows good and green, but when I pulled it up in another system, it had 500mb if free space. Ergo the 2tb cache drive.

So you might check your cache drive in another system. Couldn't hurt.

Sent from my BND-L34 using Tapatalk

Link to comment
43 minutes ago, ijuarez said:

My is 100Gb cause I may it 100GB why? I have a 2TB cache, repourposed drive from the array.

Anyhow I had this problem once, webgui kept telling me I had 135gb free on a 250gb SSD. One day everything came to a gridding halt. The cache shows good and green, but when I pulled it up in another system, it had 500mb if free space. Ergo the 2tb cache drive.

So you might check your cache drive in another system. Couldn't hurt.

Sent from my BND-L34 using Tapatalk
 

Not sure what your issue was. Sounds like some sort of filesystem corruption. Corruption seems to be related to overfilling a disk also.

 

But I have helped a lot of other users who started out with a reasonable sized docker image and filled it up. So they kept trying to fix their problem by increasing the size instead of fixing their dockers.

Link to comment
Not sure what your issue was. Sounds like some sort of filesystem corruption. Corruption seems to be related to overfilling a disk also.
 
But I have helped a lot of other users who started out with a reasonable sized docker image and filled it up. So they kept trying to fix their problem by increasing the size instead of fixing their dockers.
Possibly but I'm good now, anyhow. Just thought I mentioned it.

Sent from my BND-L34 using Tapatalk

Link to comment
  • 3 weeks later...

i found it, but i don't know how to resolve this

 

Sep 24 10:51:24 THE-BEAST move: move_object: /mnt/disk3/domains/Windows 10 HBX/vdisk2.img No space left on device
Sep 24 10:51:24 THE-BEAST root: mover: finished

 

but the file is already on disk 3, and not in the cache disk.

 

how to remove from mover this command ?

 

file is physically in

 

disk3

/mnt/user/domains

/mnt0/user/domains

 

Edited by ibasaw
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.