unRAID Server Release 6.0-beta14b-x86_64 Available

[jonp]

We will be updating to 1.5 before final. Yes.

 

Great news!

 

Will DockerMan be updated to allow new port range values?

 

Currently adding portA-portB range into DockerMan "Add Container" dialogue will not allow you proceed, even for Docker 1.4.1 to subsequently fail.

 

Thanks!

I'm sure we will. Premature to discuss specifics but I think 1.5 also provides better resource usage reporting for us as well (like CPU / memory).  I think we are going to update the tool to display those values as well.

 

is that a segway into resource allocation ? cpu pinning etc from dockerman ?

 

Lol, and the ball just keeps rolling down the hill ;-)

 

Longer term, I want to build a resource management system that handles CPU pinning between both Docker Containers and Virtual Machines. Something that keeps track of which cores are doing what and alter the context menus when adding / editing apps and vms so that you know how much you have subscribed to each core in your system.  Not a 6.0 feature, but eventually that is something I think that could be of a lot of value.

 

[tdallen]

My upgrade to 6.0beta14b is complete, it went well.  I had some of the typical problems - had to clear cache on my browser to get docker management functions to work and reset the notifications for disk temperature.  I've got one odd item in my system log, though.  This is after about 6 hours of uptime and was probably as I accessed the GUI after several hours of inactivity.

 

Mar 15 21:06:10 Tower kernel: ------------[ cut here ]------------
Mar 15 21:06:10 Tower kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x195/0x1fb() (Minor Issues)
Mar 15 21:06:10 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out (Network)
Mar 15 21:06:10 Tower kernel: Modules linked in: veth xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables md_mod ata_piix i2c_i801 pata_jmicron r8169 ahci mii libahci mvsas libsas scsi_transport_sas asus_atk0110 acpi_cpufreq [last unloaded: md_mod] (Drive related)
Mar 15 21:06:10 Tower kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.18.5-unRAID #3 (Errors)
Mar 15 21:06:10 Tower kernel: Hardware name: System manufacturer System Product Name/P5B, BIOS 2104    03/09/2009
Mar 15 21:06:10 Tower kernel: 0000000000000009 ffff88021fc03dc8 ffffffff815f76e5 000000000000dea0
Mar 15 21:06:10 Tower kernel: ffff88021fc03e18 ffff88021fc03e08 ffffffff81041c0b ffff88021fc11580
Mar 15 21:06:10 Tower kernel: ffffffff81536b8a ffff880214fc6000 ffff8800ba04a400 ffff880214fc6360
Mar 15 21:06:10 Tower kernel: Call Trace: (Errors)
Mar 15 21:06:10 Tower kernel: <IRQ>  [<ffffffff815f76e5>] dump_stack+0x46/0x58
Mar 15 21:06:10 Tower kernel: [<ffffffff81041c0b>] warn_slowpath_common+0x77/0x91
Mar 15 21:06:10 Tower kernel: [<ffffffff81536b8a>] ? dev_watchdog+0x195/0x1fb
Mar 15 21:06:10 Tower kernel: [<ffffffff81041c66>] warn_slowpath_fmt+0x41/0x43
Mar 15 21:06:10 Tower kernel: [<ffffffff81536b8a>] dev_watchdog+0x195/0x1fb
Mar 15 21:06:10 Tower kernel: [<ffffffff810522fa>] ? cancel_delayed_work+0x68/0x68
Mar 15 21:06:10 Tower kernel: [<ffffffff815369f5>] ? dev_graft_qdisc+0x69/0x69
Mar 15 21:06:10 Tower kernel: [<ffffffff815369f5>] ? dev_graft_qdisc+0x69/0x69
Mar 15 21:06:10 Tower kernel: [<ffffffff8107bc9b>] call_timer_fn.isra.28+0x18/0x70
Mar 15 21:06:10 Tower kernel: [<ffffffff8107c778>] run_timer_softirq+0x1f1/0x273
Mar 15 21:06:10 Tower kernel: [<ffffffff81044b93>] __do_softirq+0xcd/0x1c6
Mar 15 21:06:10 Tower kernel: [<ffffffff81044e24>] irq_exit+0x40/0x87
Mar 15 21:06:10 Tower kernel: [<ffffffff8102fb10>] smp_apic_timer_interrupt+0x41/0x4e
Mar 15 21:06:10 Tower kernel: [<ffffffff815fdf7d>] apic_timer_interrupt+0x6d/0x80
Mar 15 21:06:10 Tower kernel: <EOI>  [<ffffffff8103603c>] ? native_safe_halt+0x6/0x8
Mar 15 21:06:10 Tower kernel: [<ffffffff8101277b>] default_idle+0x9/0xd
Mar 15 21:06:10 Tower kernel: [<ffffffff81012e6b>] arch_cpu_idle+0xa/0xc
Mar 15 21:06:10 Tower kernel: [<ffffffff8106bdee>] cpu_startup_entry+0x12c/0x27a
Mar 15 21:06:10 Tower kernel: [<ffffffff815eb0ae>] rest_init+0x72/0x74
Mar 15 21:06:10 Tower kernel: [<ffffffff818aded1>] start_kernel+0x40c/0x419
Mar 15 21:06:10 Tower kernel: [<ffffffff818ad8bc>] ? set_init_arg+0x57/0x57
Mar 15 21:06:10 Tower kernel: [<ffffffff818ad120>] ? early_idt_handlers+0x120/0x120
Mar 15 21:06:10 Tower kernel: [<ffffffff818ad4c6>] x86_64_start_reservations+0x2a/0x2c
Mar 15 21:06:10 Tower kernel: [<ffffffff818ad5b6>] x86_64_start_kernel+0xee/0xfd
Mar 15 21:06:10 Tower kernel: ---[ end trace b3637c2958b64831 ]---
Mar 15 21:06:10 Tower kernel: r8169 0000:03:00.0 eth0: link up (Network)

 

Anything to be worried about?  I'm not seeing any bad behavior, but I'm also not used to seeing stack traces in the log.

 

Thanks.

[PeterB]

What do these errors mean, while checking for docker updates:

Mar 17 20:42:09 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/dockerupdate.php
Mar 17 20:42:09 Tower php: Updating templates...
Mar 17 20:42:15 Tower php: #012Warning: unlink(/tmp/tmp-1432048464.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:20 Tower php: #012Warning: unlink(/tmp/tmp-575547272.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: #012Warning: unlink(/tmp/tmp-1132603075.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: Updating info...
Mar 17 20:42:33 Tower php: #012bc7dde89 => bc7dde89
Mar 17 20:42:38 Tower php: #012ae38bc9a =>
Mar 17 20:42:45 Tower php: #012 => 5dbd6f5d
Mar 17 20:42:52 Tower php: #012db8e6cd9 => db8e6cd9
Mar 17 20:43:00 Tower php: #012e6c57157 =>
Mar 17 20:43:08 Tower php: #012566c91aa => 566c91aa
Mar 17 20:43:08 Tower php: Done.

 

After this happens, spme of the dockers are showing a version: "not available".

[smdion]

What do these errors mean, while checking for docker updates:

Mar 17 20:42:09 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/dockerupdate.php
Mar 17 20:42:09 Tower php: Updating templates...
Mar 17 20:42:15 Tower php: #012Warning: unlink(/tmp/tmp-1432048464.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:20 Tower php: #012Warning: unlink(/tmp/tmp-575547272.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: #012Warning: unlink(/tmp/tmp-1132603075.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: Updating info...
Mar 17 20:42:33 Tower php: #012bc7dde89 => bc7dde89
Mar 17 20:42:38 Tower php: #012ae38bc9a =>
Mar 17 20:42:45 Tower php: #012 => 5dbd6f5d
Mar 17 20:42:52 Tower php: #012db8e6cd9 => db8e6cd9
Mar 17 20:43:00 Tower php: #012e6c57157 =>
Mar 17 20:43:08 Tower php: #012566c91aa => 566c91aa
Mar 17 20:43:08 Tower php: Done.

 

After this happens, spme of the dockers are showing a version: "not available".

 

I got that on a brand new install, when my DNS was incorrect.  When I added DNS into unRAID network settings it fixed those errors.

[PeterB]

What do these errors mean, while checking for docker updates:

Mar 17 20:42:09 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/dockerupdate.php
Mar 17 20:42:09 Tower php: Updating templates...
Mar 17 20:42:15 Tower php: #012Warning: unlink(/tmp/tmp-1432048464.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:20 Tower php: #012Warning: unlink(/tmp/tmp-575547272.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: #012Warning: unlink(/tmp/tmp-1132603075.tar.gz): No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/dockerClient.php on line 157
Mar 17 20:42:25 Tower php: Updating info...
Mar 17 20:42:33 Tower php: #012bc7dde89 => bc7dde89
Mar 17 20:42:38 Tower php: #012ae38bc9a =>
Mar 17 20:42:45 Tower php: #012 => 5dbd6f5d
Mar 17 20:42:52 Tower php: #012db8e6cd9 => db8e6cd9
Mar 17 20:43:00 Tower php: #012e6c57157 =>
Mar 17 20:43:08 Tower php: #012566c91aa => 566c91aa
Mar 17 20:43:08 Tower php: Done.

 

After this happens, spme of the dockers are showing a version: "not available".

 

I got that on a brand new install, when my DNS was incorrect.  When I added DNS into unRAID network settings it fixed those errors.

But this isn't a brand new install.  It's a system which has been running for a long time, updated as new releases come along.  The network configuration has not been changed and a docker update check ran perfectly well just a couple of days ago.  Three hours after the episode above, docker update ran without error.

 

I guess that some temporary disruption to dns service and/or network connectivity might have caused this.

[tr0910]

Just got a test 14b server into a state of confusion.  Had 6 drives installed and parity protected, but had a power bump.

 

At the same time as I powered it back up, I added disk7.  It tried to do a parity check and a format at the same time and the gui hung for several hours.

 

I had to reboot and the array is now in a state with a redballed disk7, but disk7 is unassigned.

 

Since it is only a test server it's not a big deal, but strange anyway.  I think the correct way forward is a New Config???

 

[chickensoup]

Just got a test 14b server into a state of confusion.  Had 6 drives installed and parity protected, but had a power bump.

 

At the same time as I powered it back up, I added disk7.  It tried to do a parity check and a format at the same time and the gui hung for several hours.

 

I had to reboot and the array is now in a state with a redballed disk7, but disk7 is unassigned.

 

Since it is only a test server it's not a big deal, but strange anyway.  I think the correct way forward is a New Config???

Your test server has more storage than my primary server :-(

[tr0910]

Your test server has more storage than my primary server :-(

 

I am sorry.  I had purchased 2-4tb drives over a year ago that I hadn't needed yet as my data growth has slowed down.  It's just my stupidity that results in me using 4tb drives in test servers.

[dlandon]

I got these errors in the syslog and logging has stopped.

 

Mar 20 04:53:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:54:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:55:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:56:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:57:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:58:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:59:02 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:00:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:01:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:02:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:03:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /de

[WeeboTech]

I got these errors in the syslog and logging has stopped.

 

Mar 20 04:53:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:54:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:55:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:56:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:57:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:58:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 04:59:02 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:00:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:01:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:02:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Mar 20 05:03:01 MediaServer crond[1537]: exit status 2 from user root /usr/lib/sa/sa1 1 1 &> /de

 

 

Check how much space is used in /var/log, if it's full you can resize it and/or run the logrotate command.

 

Syslog has stopped updating

http://lime-technology.com/forum/index.php?topic=38805.msg360997#msg360997

 

I had suggested an adjustment to catch this condition.

 

Notifications for disk space on / and /var/log plus a bar graph or space used.

http://lime-technology.com/forum/index.php?topic=38813.0

 

 

[Ockingshay]

Well i've joined the V6 club and i have to congratulate everyone from community contributors like Bergware and Andrew (plus so many more) to the unRAID team and everyone in-between to what you have achieved. I've only scratched the service of what is available to us now and i'm blown away by what i can do with it. There is so much more it can do from when i started on version 4.7. TBH most of it is completely wasted on me (i'm attempting to learn) but this has become so invaluable to me and my family's digital life.

 

So without being overly dramatic, a simple "Well Done Team" will suffice

 

On a side note....TomM looks completely different to what i imagined you to look like hehe! http://lime-technology.com/team/

[jjslegacy]

Booted up the server and watched a movie over serviio  but came back later and I see lots of this in the alert log:

 

Mar 25 16:00:01 MJMS logger: /usr/local/sbin/mover: line 41: echo: write error: No space left on device

 

I don't see any space issues though?

tmpfs          128M  4.5M  124M  4% /var/log

/dev/sda1        15G  287M  15G  2% /boot

/dev/md1        2.8T  2.6T  132G  96% /mnt/disk1

/dev/md2        2.8T  2.4T  350G  88% /mnt/disk2

/dev/md3        2.8T  2.7T  84G  98% /mnt/disk3

/dev/md4        2.8T  2.6T  230G  92% /mnt/disk4

/dev/md5        2.8T  850G  1.9T  31% /mnt/disk5

/dev/md6        2.8T  33M  2.8T  1% /mnt/disk6

/dev/sdg1      120G  51G  69G  43% /mnt/cache

shfs            14T  11T  2.7T  81% /mnt/user0

shfs            14T  12T  2.8T  81% /mnt/user

/dev/loop0      50G  40G  9.5G  81% /var/lib/docker

 

 

What am I missing?

 

Guessing it was a memory issue but I didn't see anything hogging a lot of RAM just the OS itself. 

[smashingtool]

Sorry, I haven't been following 6.0 closely. When it comes to the new file systems, is there some way to convert to them without backing up all files onto other devices and formatting?

 

 

[BRiT]

Sorry, I haven't been following 6.0 closely. When it comes to the new file systems, is there some way to convert to them without backing up all files onto other devices and formatting?

No.

[Ockingshay]

Not for this thread but is there some sort of break down as to the different file systems and reasons why one would choose to reformat into one? I'm still on reisers (as default form v5) but am interested to know if it's worth changing.

[BRiT]

Not for this thread but is there some sort of break down as to the different file systems and reasons why one would choose to reformat into one? I'm still on reisers (as default form v5) but am interested to know if it's worth changing.

 

Use the search. There are other topics where each one has been discussed and talked about.

[itimpi]

Not for this thread but is there some sort of break down as to the different file systems and reasons why one would choose to reformat into one? I'm still on reisers (as default form v5) but am interested to know if it's worth changing.

I think in simple terms:

• Reiserfs seems to be reaching end-of-life, so there is likely to be support issues going forward on new Linux kernels. LimeTech therefore needed to position themselves with an alternative for the future.  Having said that the reiserfsck tool seems to be capable of recovering from even extreme levels of corruption and has served unRAID users well.
  
• XFS is seen as a mainline Linux file system that is widely used and can thus be considered to be well-tested and supported for the foreseeable future.  The recovery tools also seem robust and stable.  However I am not sure if unRAID users yet have much experience on how it will handle any sort of extreme FS corruption so that is still a grey area.
  
• BTRFS is a more modern and advanced file system than XFS and has functionality to protect against 'bit rot' type data corruption (as well as other advanced features).  It is not as well-tried as XFS and the recovery tools are not as good.  having said that it looks like it could become a preferred filing system in the Linux world going forward if the main Linux distributions decide to adopt it.
  

[Frank1940]

Not for this thread but is there some sort of break down as to the different file systems and reasons why one would choose to reformat into one? I'm still on reisers (as default form v5) but am interested to know if it's worth changing.

I think in simple terms:

• Reiserfs seems to be reaching end-of-life, so there is likely to be support issues going forward on new Linux kernels. LimeTech therefore needed to position themselves with an alternative for the future.  Having said that the reiserfsck tool seems to be capable of recovering from even extreme levels of corruption and has served unRAID users well.
  

 

As an added piece of information on Reiserfs, the principle developer is currently serving time in California for murder.  Future development plans seem to be up in the air  and the company which was doing the work is listed with the State of California with a status of "Suspended".

[Wimpie]

My take on this: Reiserfs is VERY buggy!!!

 

It was impossible to fill up the drives to nearly full while using Reiserfs (some people said this was with ALL filesystems, but that was not my experience, only RFS was giving me big problems), I constantly got timeouts and it was slow.

 

Now using XFS and my drives are filled up with only 791 to 260 MB free. I could only dream about this with Reiserfs.

 

And they fill up without 1 timeout or slowdown. If I want to copy another small file to these drives, then this just works. 

 

I don't know/use BTRFS, but it seems to me to be still somewhat immature...

 

In short: dump ReiserFS as soon as possible!

 

[SSD]

My take on this: Reiserfs is VERY buggy!!!

 

It was impossible to fill up the drives to nearly full while using Reiserfs (some people said this was with ALL filesystems, but that was not my experience, only RFS was giving me big problems), I constantly got timeouts and it was slow.

 

Now using XFS and my drives are filled up with only 791 to 260 MB free. I could only dream about this with Reiserfs.

 

And they fill up without 1 timeout or slowdown. If I want to copy another small file to these drives, then this just works. 

 

I don't know/use BTRFS, but it seems to me to be still somewhat immature...

 

In short: dump ReiserFS as soon as possible!

 

I am in agreement about RFS getting old. But, in its defense, it was built in a time when drive sizes were measured in gigabytes not terabytes. My early experiences with it were fine, back in the 500G and 750G days. But as the drives get bigger the performance gets worse. Anyone that was complacent about using it got a wakeup call with the recent problems. Those were maybe thinking it was old and stable and now thinking it is old and not well maintained. For me, it has never set well with me using a file system invented by a man that murdered his wife, so there is no nostalgic feeling about it for me. I have always referred to it as RFS, rather than mentioning the murderers name. And I am glad that it is off my production array (my backup array is still full of it but that is going to change very soon as I reconfigure it.

 

As for XFS, it is hugely better performance. I dare say "night and day". I am not sure about the recovery tools - we may have to pay for them. But it is best not to get into big trouble in the first place! And that means understanding the basics about how unRAID works to avoid the most common need to such recovery tools - human error.

[jbartlett]

The biggest difference I saw between reiserfs vs XFS was when deleting large multi-gig files. It would take 20-40 seconds to delete on reiserfs but barely noticeable delay on XFS.

[Ockingshay]

interesting replies...thanks all.

 

Now to the task of reformatting all my disks, whilst juggling the data on it

[spamalam]

Problems with BTRFS for me in this release, here's the kernel panic:

BTRFS info (device loop0): no csum found for inode 1723 start 1994752
BTRFS info (device loop0): no csum found for inode 1723 start 1998848
BTRFS info (device loop0): no csum found for inode 1723 start 2002944
BTRFS info (device loop0): no csum found for inode 1723 start 2007040
BTRFS info (device loop0): no csum found for inode 1723 start 2011136
BTRFS info (device loop0): no csum found for inode 1723 start 2015232
BTRFS info (device loop0): no csum found for inode 1723 start 2019328
BTRFS info (device loop0): no csum found for inode 1723 start 2023424
BTRFS info (device loop0): no csum found for inode 1723 start 2027520
BTRFS info (device loop0): no csum found for inode 1723 start 2031616
BTRFS info (device loop0): no csum found for inode 1723 start 2035712
BTRFS info (device loop0): no csum found for inode 1723 start 2039808
BTRFS info (device loop0): no csum found for inode 1723 start 2043904
BTRFS info (device loop0): no csum found for inode 1723 start 2048000
BTRFS info (device loop0): no csum found for inode 1723 start 2052096
BTRFS info (device loop0): no csum found for inode 1723 start 2056192
BTRFS info (device loop0): no csum found for inode 1723 start 2060288
BTRFS info (device loop0): no csum found for inode 1723 start 2064384
BTRFS info (device loop0): no csum found for inode 1723 start 2068480
BTRFS info (device loop0): no csum found for inode 1723 start 2072576
BTRFS info (device loop0): no csum found for inode 1723 start 2076672
BTRFS info (device loop0): no csum found for inode 1723 start 2080768
BTRFS info (device loop0): no csum found for inode 1723 start 2084864
BTRFS info (device loop0): no csum found for inode 1723 start 2088960
BTRFS info (device loop0): no csum found for inode 1723 start 2093056
BTRFS info (device loop0): no csum found for inode 1723 start 167936
docker0: port 1(veth6a1399b) entered disabled state
device veth6a1399b left promiscuous mode
docker0: port 1(veth6a1399b) entered disabled state
btrfs_dev_stat_print_on_error: 6652 callbacks suppressed
BTRFS: bdev /dev/sdk1 errs: wr 7, rd 162176, flush 0, corrupt 0, gen 0
BTRFS: bdev /dev/sdk1 errs: wr 7, rd 162177, flush 0, corrupt 0, gen 0
BTRFS: bdev /dev/sdk1 errs: wr 7, rd 162178, flush 0, corrupt 0, gen 0
BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
IP: [<ffffffff812a2b40>] __btrfs_abort_transaction+0x4d/0xff
PGD 103f30067 PUD 103dfc067 PMD 0
Oops: 0000 [#6] SMP
Modules linked in: veth xt_nat ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 nf_nat iptable_filter ip_tables md_mod i2c_i801 e1000e ptp ahci pps_core libahci
CPU: 3 PID: 566 Comm: umount Tainted: G      D W      3.18.5-unRAID #3
Hardware name: Supermicro X7SPA-HF/X7SPA-HF, BIOS 1.2        09/14/11
task: ffff88008d179020 ti: ffff880006e00000 task.ti: ffff880006e00000
RIP: 0010:[<ffffffff812a2b40>]  [<ffffffff812a2b40>] __btrfs_abort_transaction+0x4d/0xff
RSP: 0018:ffff880006e03c48  EFLAGS: 00010283
RAX: ffff88013961e000 RBX: 00000000fffffffb RCX: 0000000000000a9f
RDX: ffffffff8163f1a0 RSI: ffff880006985000 RDI: 0000000000000000
RBP: ffff880006e03c78 R08: 00000000fffffffb R09: ffff8800a6730100
R10: 0000000000000000 R11: ffff880006985000 R12: ffff880006985000
R13: 0000000000000000 R14: ffffffff8163f1a0 R15: 0000000000000a9f
FS:  00002b65d1deae00(0000) GS:ffff88013fd80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000028 CR3: 0000000103dfe000 CR4: 00000000000007e0
Stack:
ffff88013961e068 ffff880006985000 0000000000000000 ffff88013961e068
000000000063ef80 000000000063ef80 ffff880006e03cd8 ffffffff812f7bab
0000000000000003 ffff8801391dd000 0000000000000001 0000000000000000
Call Trace:
[<ffffffff812f7bab>] free_log_tree+0x57/0xca
[<ffffffff812f73a6>] ? join_running_log_trans+0x57/0x57
[<ffffffff812fd63b>] btrfs_free_log+0x17/0x26
[<ffffffff812c2a95>] btrfs_drop_and_free_fs_root+0x62/0x94
[<ffffffff812c2b8b>] btrfs_free_fs_roots+0xc4/0x102
[<ffffffff815fa86c>] ? wait_for_completion+0x18/0x1a
[<ffffffff812c43cb>] close_ctree+0x1d0/0x29a
[<ffffffff8110ce83>] ? evict_inodes+0xef/0xfe
[<ffffffff812a1e9e>] btrfs_put_super+0x14/0x16
[<ffffffff810f91af>] generic_shutdown_super+0x6e/0xea
[<ffffffff810f9429>] kill_anon_super+0xe/0x19
[<ffffffff812a1c7a>] btrfs_kill_super+0x13/0x8f
[<ffffffff810f971d>] deactivate_locked_super+0x3b/0x50
[<ffffffff810f9bed>] deactivate_super+0x3a/0x3e
[<ffffffff8110f704>] cleanup_mnt+0x54/0x74
[<ffffffff8110f75a>] __cleanup_mnt+0xd/0xf
[<ffffffff810562f4>] task_work_run+0x7e/0x96
[<ffffffff8100ab4c>] do_notify_resume+0x55/0x66
[<ffffffff815fd420>] int_signal+0x12/0x17
Code: 01 00 00 f0 0f ba a8 28 0d 00 00 02 72 1d 48 c7 c2 8b a3 76 81 44 89 c1 be 04 01 00 00 48 c7 c7 1c a1 76 81 31 c0 e8 e5 f0 d9 ff <49> 83 7d 28 00 66 41 89 5d 50 75 35 83 c3 1e 49 c7 c0 fb dd 74
RIP  [<ffffffff812a2b40>] __btrfs_abort_transaction+0x4d/0xff
RSP <ffff880006e03c48>
CR2: 0000000000000028
---[ end trace cfa7766fd11243cd ]---
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
docker0: port 5(veth5653070) entered disabled state
device veth5653070 left promiscuous mode
docker0: port 5(veth5653070) entered disabled state

 

edit and syslog

syslog.tar.gz

[jbartlett]

interesting replies...thanks all.

 

Now to the task of reformatting all my disks, whilst juggling the data on it

 

I'd recommend getting a new drive and go through your array copying the files onto it, formatting the source, and then copying the files back. Then either add the new drive to your array or upgrade one of the drives.

[Ockingshay]

interesting replies...thanks all.

 

Now to the task of reformatting all my disks, whilst juggling the data on it

 

I'd recommend getting a new drive and go through your array copying the files onto it, formatting the source, and then copying the files back. Then either add the new drive to your array or upgrade one of the drives.

 

I haven't really thought about the best way yet as i have 17TB of data across 10 drives. I use drive cages (4 drives) in each cage, so will probably add another cage of drives and format those in XFS. Then it gives me some space to move around the data.