Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Disk Useage in Pools incorrectly reported

Description

This is in Scale RC2

A bunch of HDD's.

Assign them to a pool and then look at Storage/Disks. Only some of the disks indicate as assigned to the new pool, the rest are N/A.

What might be relavent is that I assigned sda, sdb, sdc, sdd, sdf (missing sde as its running badblocks). The first disk that is missing its pool is sdf and onwards

See: https://www.truenas.com/community/threads/scale-disks.98732/#post-681396

This is repeatable

A reboot sorts this out - but one can't always reboot

Debug attached

Problem/Justification

None

Impact

None

Activity

Show:

Sean Nugent 
February 28, 2022 at 6:03 AM

Found this in TrueNAS Core 12.0-U8 as well. Exactly the same issue

Sean Nugent 
February 11, 2022 at 9:56 PM
(edited)

Sorry about that. Its a test system and subject to me "buggering" around with it from time to time.

Some of the disks had bad blocks, so I erased the pool, recreated with the disks that had no bad blocks and am running badblocks on all the remaining "bad" disks to see if I can reduce the warnings to zero

New files attached as requested

Vladimir Vinogradenko 
February 11, 2022 at 7:59 PM

sorry, can you please attach the following files (running the commands again) and take a new debug? Your pool configuration seems to be have changed since then.

Sean Nugent 
February 10, 2022 at 12:54 PM

As requested

Vladimir Vinogradenko 
February 10, 2022 at 12:45 PM

is your system in invalid state now? Can you please attach here the following files?
midclt call datastore.query storage.disk > /tmp/disk.txt
midclt call zfs.pool.query > /tmp/pool.txt

Duplicate

Details

Assignee

Reporter

Labels

Impact

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created February 6, 2022 at 10:23 PM
Updated July 6, 2022 at 8:57 PM
Resolved March 4, 2022 at 8:23 PM