unRAID Server Release 6.0-beta8-x86_64 Available


limetech

Recommended Posts

  • Replies 190
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

How do I configure docker, to run on cache drive only?

 

I want all Docker related data on my chache drive. So if a Docker is idling, only the cache disk is spun up!

place the docker.img image on a cache-only share. i put it inside my appdata share, so everything about docker (the image and the configuration files of the apps) are in that one cache-only share

Link to comment

How will mounting the Docker image file on an array disk effect it's ability to spin down? During normal operation is the image file used infrequently enough to allow the array drive to stay spun down for long periods? To me the advantages of it residing on an array drive is the fault tolerance of parity. The potential disadvantage is it won't allow spin-down of the array drive.

 

Kudos to Tom and the Limetech team for getting this beta out so quickly!

Link to comment

How will mounting the Docker image file on an array disk effect it's ability to spin down? During normal operation is the image file used infrequently enough to allow the array drive to stay spun down for long periods? To me the advantages of it residing on an array drive is the fault tolerance of parity. The potential disadvantage is it won't allow spin-down of the array drive.

 

Kudos to Tom and the Limetech team for getting this beta out so quickly!

Presumably fault tolerance of a cache only share would be provided by the cache pool feature. If i understand correctly, that way you get all the upsides, without the downsides?

Link to comment

How will mounting the Docker image file on an array disk effect it's ability to spin down? During normal operation is the image file used infrequently enough to allow the array drive to stay spun down for long periods? To me the advantages of it residing on an array drive is the fault tolerance of parity. The potential disadvantage is it won't allow spin-down of the array drive.

I do not think there can be a definitive answer to this - it will depend on the specific docker containers.

 

However I think as initial working assumption you should probably go with the dockers keeping the drive spun up (and thus probably also the parity drive if writes are involved).

Link to comment

Just an FYI folks, I'll be working on an FAQ / recap post about beta 8 for posting.  If you have questions that you feel should be answered in there, post them up and I'll make sure to include them.  Keep those posts in this thread.

 

FAQ request: now that we have three options for the file system of our array drives, what does LimeTech recommend we do?

[*]Stick with ReiserFS

[*]Convert to XFS

[*]Convert to btrfs

Also, I assume our arrays can include a mix, with different filesystems on different drives in the array.  Is this correct?

 

If we plan to convert to a new filesystem, do you recommend we try to convert the entire array in a short timeframe, or just use the preferred filesystem as we add drives?

 

Thanks!

Link to comment

Anyone still running XEN VMs in these later betas?

 

I'm still on 5a (i think) so I was waiting to move to a docker supported version, and that waiting got longer and longer since the vm just "works".

 

Can I upgrade to beta8, and then start working on moving my apps in XEN over to docker versions, while keeping them going on the VM until I'm ready?

 

If so (and since i don't have to convert my cache filesystem any longer) it seems like it should be easy to move over now?

Link to comment

Anyone still running XEN VMs in these later betas?

 

I'm still on 5a (i think) so I was waiting to move to a docker supported version, and that waiting got longer and longer since the vm just "works".

 

Can I upgrade to beta8, and then start working on moving my apps in XEN over to docker versions, while keeping them going on the VM until I'm ready?

 

If so (and since i don't have to convert my cache filesystem any longer) it seems like it should be easy to move over now?

 

I am running a Debian VM on beta8 and it works just fine.

 

EDIT:  It's a Xen VM.

Link to comment

Anyone still running XEN VMs in these later betas?

 

I'm still on 5a (i think) so I was waiting to move to a docker supported version, and that waiting got longer and longer since the vm just "works".

 

Can I upgrade to beta8, and then start working on moving my apps in XEN over to docker versions, while keeping them going on the VM until I'm ready?

 

If so (and since i don't have to convert my cache filesystem any longer) it seems like it should be easy to move over now?

 

I'm running Xen with Arch loaded up with Plex Media Server, Transmission, and Transmission-rss.  I also have another arch VM (started as a copy) that I use for testing like trying (and failing) to get WINE up and running.  Also for reference I am NOT running with any cpus pinned.  Both unraid-dom0 and Arch-domU get full access to all 8 of my cores and I let Xen scheduler figure it out.  So far no problems at all.  My schedules don't really have a chance to run a parity check and plex transcoding at the same time, but I tested it once for about 30 min and it worked perfectly.  I've been doing that since beta5a.  Unraid-dom0 gets 2048MB (min and max).

Link to comment

All seems to be working great, just re-downloading images now. Thanks!

 

I wasn't 100% sure of the update order but i did the following.

 

Deleted docker plg from plugins.

Updated unraid to beta8 & reboot

Ran btrfs subvolume delete

Started docker and added new img path

Ran  CP for existing template move

Deleted -boot/config/plugins/dockerMan.plg - /Docker-startup.plg  - /dockerMan-2014.08.28.tar.gz

 

Ran this same process, so far so good. Yet to test anything on it though (plex, etc.). But I was able to re-download images just fine using my previous templates.

 

Did a reboot with all docker images set to auto start, things came up like they did in beta6.

 

APC UPS appears to still be working, status is good in the UI (untested though by unplugging power to UPS).

 

Appreciate the walkthrough! I'll update once I've started using it for watching shows.

 

Watched a few things last night without issue.

Link to comment

What's this? Why am I getting these messages?

 

Sep  3 19:38:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 941879777 expected csum 3038475726
Sep  3 19:38:24 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1828596017 expected csum 3038475726
Sep  3 19:38:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2832518305 expected csum 3038475726
Sep  3 19:38:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 6883105 expected csum 3038475726
Sep  3 19:38:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2157543843 expected csum 3038475726
Sep  3 19:38:29 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2729550668 expected csum 3038475726
Sep  3 19:38:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1193941000 expected csum 3038475726
Sep  3 19:38:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2172697789 expected csum 3038475726
Sep  3 19:38:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2485259712 expected csum 3038475726
Sep  3 19:38:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1908356721 expected csum 3038475726
Sep  3 19:38:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 921021548 expected csum 3038475726
Sep  3 19:38:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1218586503 expected csum 3038475726
Sep  3 19:38:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 312398306 expected csum 3038475726
Sep  3 19:38:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4186015190 expected csum 3038475726
Sep  3 19:38:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2435752438 expected csum 3038475726
Sep  3 19:38:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2540469548 expected csum 3038475726
Sep  3 19:38:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2267664642 expected csum 3038475726
Sep  3 19:38:43 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1529972118 expected csum 3038475726
Sep  3 19:38:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3851408705 expected csum 3038475726
Sep  3 19:38:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3583886127 expected csum 3038475726
Sep  3 19:38:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3908626968 expected csum 3038475726
Sep  3 19:38:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1623424418 expected csum 3038475726
Sep  3 19:38:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3497563586 expected csum 3038475726
Sep  3 19:38:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3192442981 expected csum 3038475726
Sep  3 19:38:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2544940046 expected csum 3038475726
Sep  3 19:38:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1692009821 expected csum 3038475726
Sep  3 19:38:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2926946907 expected csum 3038475726
Sep  3 19:38:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 208950530 expected csum 3038475726
Sep  3 19:38:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1875966847 expected csum 3038475726
Sep  3 19:38:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 822495346 expected csum 3038475726
Sep  3 19:38:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1976928265 expected csum 3038475726
Sep  3 19:38:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1527979514 expected csum 3038475726
Sep  3 19:39:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3827120606 expected csum 3038475726
Sep  3 19:39:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4241077043 expected csum 3038475726
Sep  3 19:39:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2257142250 expected csum 3038475726
Sep  3 19:39:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3728326295 expected csum 3038475726
Sep  3 19:39:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1574203534 expected csum 3038475726
Sep  3 19:39:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1111781376 expected csum 3038475726
Sep  3 19:39:07 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1629342684 expected csum 3038475726
Sep  3 19:39:08 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 838176165 expected csum 3038475726
Sep  3 19:39:10 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3240675638 expected csum 3038475726
Sep  3 19:39:11 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3436946781 expected csum 3038475726
Sep  3 19:39:12 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2091816005 expected csum 3038475726
Sep  3 19:39:13 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 190336128 expected csum 3038475726
Sep  3 19:39:14 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4280345388 expected csum 3038475726
Sep  3 19:39:15 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2664147010 expected csum 3038475726
Sep  3 19:39:17 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2788966781 expected csum 3038475726
Sep  3 19:39:18 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1854302262 expected csum 3038475726
Sep  3 19:39:19 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2907888508 expected csum 3038475726
Sep  3 19:39:20 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1531916232 expected csum 3038475726
Sep  3 19:39:21 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3367006042 expected csum 3038475726
Sep  3 19:39:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4075711400 expected csum 3038475726
Sep  3 19:39:23 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4032204269 expected csum 3038475726
Sep  3 19:39:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 744115501 expected csum 3038475726
Sep  3 19:39:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3457223072 expected csum 3038475726
Sep  3 19:39:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2626928494 expected csum 3038475726
Sep  3 19:39:28 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2541581988 expected csum 3038475726
Sep  3 19:39:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2092652876 expected csum 3038475726
Sep  3 19:39:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3742300931 expected csum 3038475726
Sep  3 19:39:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 661185822 expected csum 3038475726
Sep  3 19:39:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2584543821 expected csum 3038475726
Sep  3 19:39:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3465722361 expected csum 3038475726
Sep  3 19:39:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 882030517 expected csum 3038475726
Sep  3 19:39:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4207958048 expected csum 3038475726
Sep  3 19:39:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2979258028 expected csum 3038475726
Sep  3 19:39:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1339476662 expected csum 3038475726
Sep  3 19:39:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2426288737 expected csum 3038475726
Sep  3 19:39:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1998475403 expected csum 3038475726
Sep  3 19:39:42 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2101493216 expected csum 3038475726
Sep  3 19:39:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3162668184 expected csum 3038475726
Sep  3 19:39:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1178236686 expected csum 3038475726
Sep  3 19:39:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4198409984 expected csum 3038475726
Sep  3 19:39:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1396331646 expected csum 3038475726
Sep  3 19:39:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3602559496 expected csum 3038475726
Sep  3 19:39:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1129340030 expected csum 3038475726
Sep  3 19:39:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1520628242 expected csum 3038475726
Sep  3 19:39:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3811934344 expected csum 3038475726
Sep  3 19:39:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1422485324 expected csum 3038475726
Sep  3 19:39:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 178974169 expected csum 3038475726
Sep  3 19:39:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3404343779 expected csum 3038475726
Sep  3 19:39:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 507039058 expected csum 3038475726
Sep  3 19:39:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4064631500 expected csum 3038475726
Sep  3 19:39:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1667668024 expected csum 3038475726
Sep  3 19:40:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4133590599 expected csum 3038475726
Sep  3 19:40:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2969333643 expected csum 3038475726
Sep  3 19:40:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 543778692 expected csum 3038475726
Sep  3 19:40:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2354671325 expected csum 3038475726
Sep  3 19:40:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2116785903 expected csum 3038475726
Sep  3 19:40:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4208957750 expected csum 3038475726

 

Link to comment

Can I use xfs on the cache drive? I have 6.0B8 on my second server, but it has no cache drive, so I can't check that.

 

The release notes suggest no, but a post in this thread suggest yes.

 

Cheers,

 

Neil.

 

You can use btrfs, reiserfs, or xfs when cache is a single disk.  But you can only use btrfs on a multi-device cache pool.  Further, if you have a single btrfs cache disk, you can convert it to a cache pool by adding another device to cache.  If the single cache disk is reiserfs or xfs, you cannot convert it to a pool.

Link to comment

What's this? Why am I getting these messages?

 

Sep  3 19:38:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 941879777 expected csum 3038475726
Sep  3 19:38:24 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1828596017 expected csum 3038475726
Sep  3 19:38:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2832518305 expected csum 3038475726
Sep  3 19:38:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 6883105 expected csum 3038475726
Sep  3 19:38:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2157543843 expected csum 3038475726
Sep  3 19:38:29 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2729550668 expected csum 3038475726
Sep  3 19:38:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1193941000 expected csum 3038475726
Sep  3 19:38:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2172697789 expected csum 3038475726
Sep  3 19:38:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2485259712 expected csum 3038475726
Sep  3 19:38:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1908356721 expected csum 3038475726
Sep  3 19:38:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 921021548 expected csum 3038475726
Sep  3 19:38:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1218586503 expected csum 3038475726
Sep  3 19:38:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 312398306 expected csum 3038475726
Sep  3 19:38:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4186015190 expected csum 3038475726
Sep  3 19:38:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2435752438 expected csum 3038475726
Sep  3 19:38:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2540469548 expected csum 3038475726
Sep  3 19:38:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2267664642 expected csum 3038475726
Sep  3 19:38:43 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1529972118 expected csum 3038475726
Sep  3 19:38:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3851408705 expected csum 3038475726
Sep  3 19:38:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3583886127 expected csum 3038475726
Sep  3 19:38:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3908626968 expected csum 3038475726
Sep  3 19:38:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1623424418 expected csum 3038475726
Sep  3 19:38:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3497563586 expected csum 3038475726
Sep  3 19:38:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3192442981 expected csum 3038475726
Sep  3 19:38:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2544940046 expected csum 3038475726
Sep  3 19:38:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1692009821 expected csum 3038475726
Sep  3 19:38:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2926946907 expected csum 3038475726
Sep  3 19:38:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 208950530 expected csum 3038475726
Sep  3 19:38:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1875966847 expected csum 3038475726
Sep  3 19:38:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 822495346 expected csum 3038475726
Sep  3 19:38:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1976928265 expected csum 3038475726
Sep  3 19:38:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1527979514 expected csum 3038475726
Sep  3 19:39:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3827120606 expected csum 3038475726
Sep  3 19:39:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4241077043 expected csum 3038475726
Sep  3 19:39:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2257142250 expected csum 3038475726
Sep  3 19:39:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3728326295 expected csum 3038475726
Sep  3 19:39:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1574203534 expected csum 3038475726
Sep  3 19:39:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1111781376 expected csum 3038475726
Sep  3 19:39:07 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1629342684 expected csum 3038475726
Sep  3 19:39:08 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 838176165 expected csum 3038475726
Sep  3 19:39:10 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3240675638 expected csum 3038475726
Sep  3 19:39:11 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3436946781 expected csum 3038475726
Sep  3 19:39:12 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2091816005 expected csum 3038475726
Sep  3 19:39:13 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 190336128 expected csum 3038475726
Sep  3 19:39:14 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4280345388 expected csum 3038475726
Sep  3 19:39:15 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2664147010 expected csum 3038475726
Sep  3 19:39:17 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2788966781 expected csum 3038475726
Sep  3 19:39:18 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1854302262 expected csum 3038475726
Sep  3 19:39:19 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2907888508 expected csum 3038475726
Sep  3 19:39:20 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1531916232 expected csum 3038475726
Sep  3 19:39:21 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3367006042 expected csum 3038475726
Sep  3 19:39:22 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4075711400 expected csum 3038475726
Sep  3 19:39:23 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4032204269 expected csum 3038475726
Sep  3 19:39:25 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 744115501 expected csum 3038475726
Sep  3 19:39:26 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3457223072 expected csum 3038475726
Sep  3 19:39:27 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2626928494 expected csum 3038475726
Sep  3 19:39:28 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2541581988 expected csum 3038475726
Sep  3 19:39:30 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2092652876 expected csum 3038475726
Sep  3 19:39:31 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3742300931 expected csum 3038475726
Sep  3 19:39:32 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 661185822 expected csum 3038475726
Sep  3 19:39:33 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2584543821 expected csum 3038475726
Sep  3 19:39:34 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3465722361 expected csum 3038475726
Sep  3 19:39:36 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 882030517 expected csum 3038475726
Sep  3 19:39:37 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4207958048 expected csum 3038475726
Sep  3 19:39:38 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2979258028 expected csum 3038475726
Sep  3 19:39:39 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1339476662 expected csum 3038475726
Sep  3 19:39:40 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2426288737 expected csum 3038475726
Sep  3 19:39:41 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1998475403 expected csum 3038475726
Sep  3 19:39:42 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2101493216 expected csum 3038475726
Sep  3 19:39:44 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3162668184 expected csum 3038475726
Sep  3 19:39:45 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1178236686 expected csum 3038475726
Sep  3 19:39:46 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4198409984 expected csum 3038475726
Sep  3 19:39:47 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1396331646 expected csum 3038475726
Sep  3 19:39:48 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3602559496 expected csum 3038475726
Sep  3 19:39:49 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1129340030 expected csum 3038475726
Sep  3 19:39:51 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1520628242 expected csum 3038475726
Sep  3 19:39:52 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3811934344 expected csum 3038475726
Sep  3 19:39:53 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1422485324 expected csum 3038475726
Sep  3 19:39:54 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 178974169 expected csum 3038475726
Sep  3 19:39:55 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 3404343779 expected csum 3038475726
Sep  3 19:39:56 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 507039058 expected csum 3038475726
Sep  3 19:39:58 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4064631500 expected csum 3038475726
Sep  3 19:39:59 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 1667668024 expected csum 3038475726
Sep  3 19:40:00 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4133590599 expected csum 3038475726
Sep  3 19:40:01 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2969333643 expected csum 3038475726
Sep  3 19:40:03 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 543778692 expected csum 3038475726
Sep  3 19:40:04 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2354671325 expected csum 3038475726
Sep  3 19:40:05 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 2116785903 expected csum 3038475726
Sep  3 19:40:06 HomeServer kernel: BTRFS info (device loop8): csum failed ino 23106 off 106496 csum 4208957750 expected csum 3038475726

 

Looks like the ISO has some kind of corruption.

 

You might have to do a find on the mount point with inode number to find the suspect file.

 

find (wherever the mount point is) -inum 23106 -ls

Link to comment

Which FS will be faster if I'm writing multiple files to it simultaneously (say 5)?

 

A cursory glance says XFS might be a good choice?

The tests I have seen that have been done by forum members suggest there is no discernible difference in speed between the different formats.

Thanks. I may try xfs at some point, anyhoo.

Link to comment

Hi guys I wanted to post here because i am fairly new to unraid but i wanted to make sure i do everything right befor i upgrade to the latest beta , i have everything working on beta6 i tried to upgrade to beta7 but i was having issues where i couldn't mount the array .....  I just don't want to mess everything up since i really spent much time getting docker and all of my containers to work properly.

 

I have a cache SSD which where docker is installed in /mnt/cache/docker

Now all of my docker containers are located in /mnt/cache/appdata/XXX

I am using gfjardim plugin to manage the docker container and images.

 

I have been reading the upgrade instructions but the more i read the more complicated it gets .... I want everything to upgrade but i want the docker.img and all of the containers and images to remain on the SSD cache drive. I know this might be easy to some but i am really confused with all of these new features and changes on beta8 .

 

Also i have been reading about the docker.img and i have a question regarding its size i really dont know how much space should i assign to it since i don't know if that .img file is where all of my apps and appdata will be stored..

 

I hope someone can make this clearer for some folks as me who are a bit less tech savy.

 

Thanks

 

Shremi

Link to comment

I have a cache SSD which where docker is installed in /mnt/cache/docker

Are you sure that this is the only thing installed there?  I would have thought that you would have also been installing the actual containers themselves there that are downloaded from the internet?  If so and you follow the upgrade instructions then these will be removed and the containers will be instead installed into a docker.img file (which is effectively a virtual disk for holding the actual downloaded files that make up containers).  In your case I would recommend using /mnt/cache/docker.img for these containers to keep them on the cache drive. 

Now all of my docker containers are located in /mnt/cache/appdata/XXX

I am assuming that you do not really mean the containers - but the configuration data and application data that is used by the containers and held external to the actual containers but mapped appropriately by parameters to the run command.  This is the practise that I have seen all the current dockers adhering to.  These will remain unchanged after the upgrade.

 

I am using gfjardim plugin to manage the docker container and images.

the upgrade instructions tell you how to remove this as you now want to use the version that is built-in to beta 8.  It has the same functionality, but is now integrated into unRAID.

 

In the docker section of the forum there are guidance on how you can add the latest gfjardin updates on top of the version now built in to beta 8.  It is likely that these updates will end up integrated into the next beta.

 

I have been reading the upgrade instructions but the more i read the more complicated it gets .... I want everything to upgrade but i want the docker.img and all of the containers and images to remain on the SSD cache drive. I know this might be easy to some but i am really confused with all of these new features and changes on beta8 .

I think you are thinking it is more complicated than it is.    Effectively it is just the downloaded container images that are now held in a virtual disk (docker.img), and everything else remains functioning exactly as before.  The docker manager component is now built in to unRAID rather than being a add-on.

 

Also i have been reading about the docker.img and i have a question regarding its size i really dont know how much space should i assign to it since i don't know if that .img file is where all of my apps and appdata will be stored..

You do not really need to worry too much about its size as it will be automatically extended if needed.  I would have thought that the recommended default of 10GB is a good starting point. 

 

Note that the docker.img files does NOT contain any configuration files or user data you currently have under /mnt/cache/appdata - they stay where they are.  It is used for the downloaded files that you almost certainly had under/mnt/cache/docker with beta 7.

 

Has that helped or confused you even more :)

Link to comment

A interesting note in 6b8: If you try xfs_check ( the primary tool for checking XFS disks) it returns with "xfs_check is deprecated and scheduled for removal in June 2014.  Please use xfs_repair -n instead." 

 

Something is wrong: code definitely uses 'xfs_repair', never used 'xfs_check'.  Where are you seeing this message?

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.