Cant resize poolsize

[phillxnet (Philip Guyton)]

@g6094199 Hello again.

@g6094199

OK now it gets a log clearer why its not mounting

Yes this helps.

@g6094199

Error running a command. cmd = /bin/mount -t btrfs -o subvol=mnt /dev/disk/by-id/ata-ST6000VN0033-2EE110_xxx-part1 /

It may be that you ‘switched’ (ie via command line) to whole disk without changing your re-direct role entry for the given disk. That’s all I can think of currently as to why Rockstor would ‘entertain’ a partition.

Can we have a pic of the disk page as your last picture of this in the following post indicated a redirection role was in play back then?

New disk doesnt get detected

Hi Phil! followed you order. removed the disks, deleted the disks and the pool, rebooted, everiting was removed, insert the disks again, set a redirect role on the partition of the …VN0033 disk and imported the pool. But it doesnt resulted in what we should expect. The pool was successfully added, but after a reboot the disk i added was again gone from the pool as before The “older” disks are still there! Now it looks like this: [grafik] [grafik] There must be a bug somewhere! I tried it …

I take it you have now sorted the disk that had both a whole disk and partition btrfs signature due to incomplete wipe between first a whole disk btrfs format followed by a partitioned variant? Ie I am assuming all disk members of that pool are now showing consistent blank UUID entries from the lsblk command given in that thread. And that all disk members are also whole disk btrfs?

This was my assumption following:

@g6094199

I will follow your advise and remove the partitions fom all disks step by step. Hope this will uncompicate things for now and the future.

THX!

As you log has been altered on the serial numbers can we assume there is only one by-id name with a -part1 ending as I see 2 entries that could be covered by:

ata-ST6000VN0033-2EE110_xxxx-part1

excluding the system disk elements of course.

Also:

@g6094199

… guys like me already use space_cache=v2

Note that we still don’t support space_cache=v2 as a mount option.

Hope that helps to sort things out as it’s all that springs to mind currently. Ie if a disk is still showing a redirect role in play that could account for it.