Hello Again,

 

I am getting error messages that I am out of space when trying to copy a file to my array. The file is 17.6 Gigabytes in size. My array claims it has enough space free on the drives to copy the file, per my previous post, I set my Minimum Free Space to 20GB, and have increased that to 100GB.

 

I tried to  attach my Diagnostics file but the forum claims the file must be 192KB or smaller, and my diagnostics file is 219KB so i have instead uploaded it to dropbox.

 

Diagnostic Info Download

https://www.dropbox.com/s/2ecqluiwla0l94r/unraid-diagnostics-20160504-0746.zip?dl=0

 

May 4 07:37:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 29, rd 0, flush 0, corrupt 0, gen 0
May 4 07:37:09 Unraid kernel: loop: Write error at byte offset 2185711616, length 4096.
May 4 07:37:09 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 4268968
May 4 07:37:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 30, rd 0, flush 0, corrupt 0, gen 0
May 4 07:37:13 Unraid kernel: loop: Write error at byte offset 2196852736, length 4096.
May 4 07:37:13 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 4290720
May 4 07:37:13 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 31, rd 0, flush 0, corrupt 0, gen 0
May 4 07:39:39 Unraid shfs/user: shfs_write: write: (28) No space left on device
May 4 07:39:39 Unraid shfs/user: shfs_write: write: (28) No space left on device
May 4 07:39:39 Unraid kernel: loop: Write error at byte offset 2198999040, length 4096.
May 4 07:39:39 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 4294840
May 4 07:39:39 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 32, rd 0, flush 0, corrupt 0, gen 0
May 4 07:39:39 Unraid kernel: loop: Write error at byte offset 2199085056, length 4096.
May 4 07:39:39 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 4295088
May 4 07:39:39 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 33, rd 0, flush 0, corrupt 0, gen 0
May 4 07:39:39 Unraid shfs/user: shfs_rename: rename: /mnt/cache/Media/Movies/Teenage Mutant Ninja Turtles II/Teenage_Mutant_Ninja_Turtles_II_t00.mkv /mnt/cache/Media/Movies/Teenage Mutant Ninja Turtles II/.fuse_hidden0023a91c00000007 (28) No space left on device
May 4 07:39:59 Unraid kernel: loop: Write error at byte offset 9896374272, length 4096.
May 4 07:39:59 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 19328648
May 4 07:39:59 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 34, rd 0, flush 0, corrupt 0, gen 0
May 4 07:40:09 Unraid kernel: loop: Write error at byte offset 830496768, length 4096.
May 4 07:40:09 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 1622016
May 4 07:40:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 35, rd 0, flush 0, corrupt 0, gen 0
May 4 07:42:00 Unraid emhttp: shcmd (119): :>/etc/samba/smb-shares.conf
May 4 07:42:00 Unraid avahi-daemon[4173]: Files changed, reloading.
May 4 07:42:00 Unraid emhttp: Restart SMB...
May 4 07:42:00 Unraid emhttp: shcmd (120): killall -HUP smbd
May 4 07:42:01 Unraid emhttp: shcmd (121): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service
May 4 07:42:01 Unraid avahi-daemon[4173]: Files changed, reloading.
May 4 07:42:01 Unraid avahi-daemon[4173]: Service group file /services/smb.service changed, reloading.
May 4 07:42:01 Unraid emhttp: shcmd (122): pidof rpc.mountd &> /dev/null
May 4 07:42:01 Unraid emhttp: shcmd (123): /etc/rc.d/rc.atalk status
May 4 07:42:01 Unraid avahi-daemon[4173]: Service "Unraid" (/services/smb.service) successfully established.
May 4 07:44:09 Unraid kernel: loop: Write error at byte offset 3564699648, length 4096.
May 4 07:44:09 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 6962304
May 4 07:44:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 36, rd 0, flush 0, corrupt 0, gen 0
May 4 07:44:13 Unraid shfs/user: shfs_write: write: (28) No space left on device
May 4 07:44:13 Unraid shfs/user: shfs_write: write: (28) No space left on device
May 4 07:44:13 Unraid shfs/user: shfs_write: write: (28) No space left on device
May 4 07:44:13 Unraid shfs/user: shfs_rename: rename: /mnt/cache/Media/Movies/Teenage Mutant Ninja Turtles II/Teenage_Mutant_Ninja_Turtles_II_t00.mkv /mnt/cache/Media/Movies/Teenage Mutant Ninja Turtles II/.fuse_hidden0024930500000008 (28) No space left on device
May 4 07:44:49 Unraid kernel: loop: Write error at byte offset 8334315520, length 4096.
May 4 07:44:49 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 16277960
May 4 07:44:49 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 37, rd 0, flush 0, corrupt 0, gen 0
May 4 07:45:34 Unraid kernel: loop: Write error at byte offset 3497013248, length 4096.
May 4 07:45:34 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 6830104
May 4 07:45:34 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 38, rd 0, flush 0, corrupt 0, gen 0
May 4 07:46:09 Unraid kernel: loop: Write error at byte offset 3413139456, length 4096.
May 4 07:46:09 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 6666288
May 4 07:46:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 39, rd 0, flush 0, corrupt 0, gen 0
May 4 07:46:09 Unraid kernel: loop: Write error at byte offset 8322899968, length 4096.
May 4 07:46:09 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 16255664
May 4 07:46:09 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 40, rd 0, flush 0, corrupt 0, gen 0
May 4 07:50:28 Unraid kernel: loop: Write error at byte offset 2196959232, length 4096.
May 4 07:50:28 Unraid kernel: blk_update_request: I/O error, dev loop0, sector 4290720
May 4 07:50:28 Unraid kernel: BTRFS: bdev /dev/loop0 errs: wr 41, rd 0, flush 0, corrupt 0, gen 0

 

 

Any Help is appreciated, thanks!

Your docker.img is full.

Hello mr-hexen,

 

It doesn't seem to be, if I am reading this correctly, my docker.img is 40gigs, with only 14 gigs used.

 

Try running a scrub on the cache drive and on the docker.img

I know how to run a scrub on the docker.img, but what is the proper method to run a scrub on the cache drive?

I believe from main you just click the Cache Drive, and there should be an option to run a scrub.

 

According to https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#btrfs_scrub a drive formatted in BTRFS needs to be mounted (ie: unlike other drives, you do not start the array in maintenance mode)

While Ill be darned, never saw that before, ill run it and let you guys know the results.

OK, I've scrubbed both.

 

Cache Drive Scrub

 

Docker Image Scrub

 

Not really seeing that it did anything, should I just try my copy again?

Won't hurt

 

Sent from my LG-D852 using Tapatalk

 

 

Unfortunately I am still experiencing the same problem.

 

So as far as I can tell my options are:

 

1. Bypass my cache drive, and copy file directly to array.

2. Delete my Docker Image and recreate

3. Dump BTRFS as my cache drive file system and go with xfs.

4. Replace my cache drive.

 

One thing I don't understand though, is how would a bad docker.img, cause files not to copy?

Odd, because /dev/loop0 is the mounted docker.img...what folder are you attempting to copy it to?

Hello mr-hexen,

 

I have a share called "Media" Under that share is several folders, and I am attempting to copy to \Media\Movies

 

Here are my share settings for "Media"

 

Additionally, I just tested my idea about bypassing the cache drive. I enabled the share for Drive 8 (which is the drive that has the least amount of free space) and copied directly to that drive. The copy finished with no issues. Which I believe means that there is something wrong with using my cache drive.

Your min free space is set to 100G. I bet that is the problem right there.

Hello mr-hexen,

 

Originally it was 0k, I started having the issue while it was set to 0k. So I increased it to 20G, this seemingly resolved the issue. But then the issue came back. So I increased it to 100G.

 

It is my understanding that the value for that field, basically says,  "Do not write to any drive that doesn't have at least <defined value> free" By putting 100GB, I believe I am telling unraid to not write to any drive that has under 100GB free. Is that correct?

 

What do you recommend as a value for that field?

 

Thank You

So any drive with less than 100G will return out of space errors

You'd want to set it to a value that's just higher than the size of the largest file you are likely to write to your array.

 

I notice that your disks are pretty full, and many of them are ReiserFS format, which performs badly on writes when nearly full. Perhaps they are trying to allocate space but timing out. You have some free space available but it's spread across all your disks. Have you considered moving some files around to free up more space but on fewer disks? You can fill the XFS format disks almost completely, though I'd leave a few gigabytes free.

 

I set the value to 15GB, this seems to have done the trick.

 

I now have a much better understanding of what the minumum size does to folder shares.

 

Thanks you guys!

Hello Everyone,

 

My issue is back. I have been moving drive space around to free up at least 80 gigabytes on every disk. My "Minimum Free Space" is set to 7GB, and I have excluded all disks from the share except my drive with the most free space which is included. I now believe this issue is a problem with btrfs on my cache drive. And I plan on removing everything from my cache drive and formatting it with XFS instead of BTRFS.

 

Ill update this post with my findings.

 

My diagnostics log is here https://www.dropbox.com/s/vbsc7y0pe5q7291/unraid-diagnostics-20160516-1900.zip?dl=0

 

 

Thank You

Update:

 

I zipped up all my docker containers, copied them off the cache drive. Formatted my cache drive with XFS, and set everything back up. My issue appears to be fully resolved now. I removed all disk limitations on my share, and everything is working. Something was wrong on btrfs which caused this issue, and scrubs did not resolve.

 

Thanks to everyone who helped me

and yet another report of BTRFS messing something up. This is why I recommend users avoid it if at all possible and stick w/ XFS/RFS for any/all drives.