Brandon_K Posted May 2, 2022 Share Posted May 2, 2022 I'm not sure when this occurred, so I'm unsure if this is a RC5 bug, or if this was due to how I handled replacing/consolidating a number of disks. I had a dozen drives that I consolidated down to 5. I used robo to copy each disk from the array directly to the new drives (as unassigned devices). IE, disk1 and disk2 of the array were copied to /disks/newdrive1, etc. No issues with the data copies. I went this route as the old disks were pretty slow SMR's and it was significantly faster to copy two disks at the same time to their new home. At that point, I upgraded from RC4 to RC5 and rebooted. Everything still looked good, so I shutdown, pulled the old drives, rebooted, created a new config with the 5 new drives. I reassigned the shares to the new disk config, everything looked great and parity is currently rebuilding. But when I let it compute shares, it is off wildly. The array is currently made up of 5x10tb + 2x10tb parity. No share uses more than two disks, plus some shares have 500gb of cache to work with. Yet, I'm getting a few shares reporting as multiple petabytes. Picture cropped for sake of resolution and readability. Quote Link to comment
itimpi Posted May 2, 2022 Share Posted May 2, 2022 Known bug with rc5 where size units are off by approx 1000 (I.e. PB when it should be TB). Quote Link to comment
Recommended Posts
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.