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


8 posts in this topic Last Reply

Recommended Posts

Hello,

A copy to my array is failing claiming not enough space. But my array should have enough space to make the copy.

I am getting the following errors in my log:

 

May  2 20:56:55 Unraid shfs/user: shfs_write: write: (28) No space left on device
May  2 20:56:55 Unraid shfs/user: shfs_write: write: (28) No space left on device
May  2 20:56:55 Unraid shfs/user: shfs_rename: rename: /mnt/cache/Media/Movies/<redacted>/title00.mkv /mnt/cache/Media/Movies/<redacted>/.fuse_hidden003194080000000f (28) No space left on device
May  2 21:12:45 Unraid emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog
May  2 21:14:37 Unraid shfs/user: shfs_write: write: (28) No space left on device
May  2 21:14:37 Unraid shfs/user: shfs_write: write: (28) No space left on device
May  2 21:14:38 Unraid shfs/user: shfs_rename: rename: /mnt/cache/Media/Movies/<redacted>/title00.mkv /mnt/cache/Media/Movies/<redacted>/.fuse_hidden0031940800000010 (28) No space left on device
May  2 21:15:12 Unraid kernel: loop: Write error at byte offset 8308060160, length 4096.
May  2 21:15:12 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 16226680
May  2 21:15:12 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0
May  2 21:15:12 Unraid kernel: loop: Write error at byte offset 8308187136, length 4096.
May  2 21:15:12 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 16226928
May  2 21:15:12 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0
May  2 21:16:29 Unraid emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog

 

Please help, not sure what to do. Diagnostics attached.

 

unraid-diagnostics-20160502-2117.zip

Link to post

Is your cache disk full by chance?

doesn't unraid handle this on its own??

 

It depends, if you reference /mnt/user/ on a cache enabled share... yes I think so.

 

If you reference /mnt/cache/ then I don't think it does, because it's not part of the fuse file system.

Link to post
My guess is you have your split levels, or min free space settings set in such a way that shfs attempts to put it on a disk that doesn't have space.

 

This resolved my issue. I went into the share settings and changed the value for "Min Free Space" from 0K to 20GB. Issue is now resolved.

 

Thanks!

Link to post

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.