tl;dr - Would drives connected to the MB and not the LSI card be causing my balance to take forever?
Sorry for the long post:
I recently moved from an MDRaid under Ubuntu to Rockstor to kelp keep my apps (Rockons) easier to manage/update, as well as to manage shares and general storage upkeep easier. Moving the data over was actually pretty easy, as I kept them all as single disks while breaking and shrinking the MDArray. Now that I have the MDArray removed and have all of my disks added to the Pool, Ive changed the btrfs pool to Raid10.
I am ok with losing that much space, as I was hoping to gain speed and again reduce overall management of the file system, but this is where my problems began…
I have 10ea 4TB WD Reds in one pool:
- 8ea sitting on my LSI 9211-8i
- 2ea sitting on the motherboard (Asus M5A97 Plus w/ 6 Sata ports running off of a SB950 chipset)
I also have
- 1ea “Old” 1TB WD HDD (System Drive/Rockons)
- 2ea SSD’s (kingston and intel) as another pool (plex_config and some files needed for faster access)
I have been running a balance on the “WD Reds” Pool for about a week and have made VERY little headway when looking at the btrfs balance status. I also see a ton of messages about “found extents” in dmesg from one drive, which I assume is the log when btrfs finds and moves files. It has been on one of my drives for a couple of days now, so following up on my assumptions, I started looking at where that drive is plugged in, and its on my motherboard.
The other drives haven’t logged yet, so I don’t know if this is truely the issue, but could it be possible that the drive sitting on the motherboard be causing the entire balance to slow down this much?
Thanks for making it this far, and hope that someone has a clue about this whole thing.