Scale Disks

[NugentS]

Just been playing around with Scale and spotted the following.
I have disks sda through sdk which are a bunch of scratch 3TB HDD's that I am testing with. Some are less than 100% good
In the Storage/Disks section:
sda through sdd are part of a single pool
sde through sdk are N/A
This is wrong
sda, sdb, sdc, sdd, sdg, sdh, sdj are in fact all part of the pool
sde, sdf, sdi, sdk are not assigned to any pool and are running badblocks destructively at the moment

I know this is an issue with Core, but wasn't aware it was an issue in Scale.

I will try and check on Jira if this has been logged. But thought I would highlight here

https://jira.ixsystems.com/projects/NAS/issues/NAS-113663?filter=allopenissues

 

[morganL]

It's probably a function of how the pool was created.... can you outline the steps and when the issue became clear.

Was it created in SCALE or imported from CORE?

 

[NugentS]

all created in Scale, no imports

Yesterday I had a single pool of all the HDD's. I deleted the pool and set up a smaller pool of all the disks that were reporting OK in SMART. The others are still in the server, but running badblocks

Also, I can't find the ticket in JIRA that I logged

 

[NugentS]

Strangely (or perhaps not) after a reboot the disks are now showing correctly

 

[Kris Moore]

Sounds like a middleware cache issue. Most likely the reboot forced it to re-query the drives and update that information. If you see it reproduced again later, please file a bug ticket.

 

[NugentS]

I thought I had filed a ticket.
I think I will destrooy the pool and do it again - bet it won't happen

 

[NugentS]

Actually the same does happen again - a repeatable bug - yay

I'll try and log a ticket again

Aha - its turned up - there are now two tickets - oops

https://jira.ixsystems.com/browse/NAS-114681

https://jira.ixsystems.com/browse/NAS-114668