Soon™️ 6.12 Series

[JorgeB]

On 3/24/2023 at 7:12 PM, sunbear said:

So if a user is adding multiple identical drives, can I assume that it will generally always make more sense to add a raid-protected pool rather than adding individual drives to the parity-protected array?

There are advantages and disadvantages for both:

 

array good:

• even if you lose more disks than parity can emulate the data on the remaining good disks can still be read
• any filesystem corruption will only affect that particular disk
• you can fully utilize disks of different capacities and if you upgrade just one disk its capacity can be fully used.
• you can add/remove a single disk or more at any time
• spin up only the disk being read, or parity and the disk being written to (when using default write mode)

 

array bad:

• performance
• no zfs self healing

 

Pools are basically the opposite.

 

pool good:

• performance
• zfs self healing

 

pool bad:

• if you lose more disks than the pool redundancy can recover from the complete pool is gone
• if the pool filesystem gets corrupted you can lose the whole pool, and while this is rare with zfs it can happen
• you can use disks of different capacity in raidz but it will only use the capacity of the smallest one, only when all pool disks are upgraded to a larger same size can the pool be expanded
• you cannot expand a raidz pool with a single disk (at least not for now), you can add another vdev of the same width, say for example you have a 4 disk raidz1 pool, you can add another 4 disks in raidz1 to expand it
• you cannot remove one or more disks (including a complete vdev) from a raidz pool, mirrors are more flexible but I would guess most are interested in using raidz with zfs
• any read/write to the pool will spin up all disks

 

 

I'm sure I forgot some but these should be the main ones.

[jammsen]

On 3/24/2023 at 8:31 PM, JorgeB said:

pool bad:

• if you lose more disks than the pool redundancy can recover from the complete pool is gone
• if the pool filesystem gets corrupted you can lose the whole pool, and while this is rare with zfs it can happen
• you can use disks of different capacity in raidz but it will only use the capacity of the smallest one, only when all pool disks are upgraded to a larger same size can the pool be expanded
• you cannot expand a raidz pool with a single disk (at least not for now), you can add another vdev of the same width, say for example you have a 4 disk raidz1 pool, you can add another 4 disks in raidz1 to expand it
• you cannot remove one or more disks (including a complete vdev) from a raidz pool, mirrors are more flexible but I would guess most are interested in using raidz with zfs

 

Arent thoose true for Btrfs Raid in a Pool?

[itimpi]

44 minutes ago, jammsen said:

 

Arent thoose true for Btrfs Raid in a Pool?

Only some of them:

• If a pool contains different size disks BTRFS will try and use all the available space (RAID level permitting).
• You can add new drives to the pool at any time and their space will be utilised (RAID level permitting).
• You can remove drives from the pool as long as the pool is redundant.

A point that I do not think ZFS supports (could be wrong about this) but BTRFS does is that you can dynamically switch between RAID levels.

[apandey]

6 hours ago, itimpi said:

A point that I do not think ZFS supports (could be wrong about this) but BTRFS does is that you can dynamically switch between RAID levels.

This is correct. Raid-Z level reshaping is not possible in zfs. The level needs to be decided at create

Edited April 9 by apandey

[dopeytree]

Any idea when the release candidate moves to general release?

[JonathanM]

On 12/7/2022 at 10:36 AM, JonathanM said:

Soon™️

 

[xyzeratul]

Me not really into the whole ZFS upgrade, so is there anything else interesting in 6.12?

[xaositek]

3 minutes ago, xyzeratul said:

Me not really into the whole ZFS upgrade, so is there anything else interesting in 6.12?

Dashboard Updates, AutoTrim for xfs and btrfs, Linux Multi-Gen LRU, Release bz file restructure - all kinds of stuff!

 

 

Edited April 11 by xaositek

[xyzeratul]

Just now, xaositek said:

Dashboard Updates, AutoTrim for xfs and btrfs, Linux Multi-Gen LRU, Release bz file restructure - all kinds of stuff!

Thx, Multi-Gen LRU does sound nice, never thought Unraid would support it so soon, anyway where can I find the full list feature of this upgrade?

[xaositek]

2 minutes ago, xyzeratul said:

Thx, Multi-Gen LRU does sound nice, never thought Unraid would support it so soon, anyway where can I find the full list feature of this upgrade?

 

[xaositek]

For anyone curious - test/beta builds are still happening - 6.12.0-rc2.11 just came out

[gyto6]

10 hours ago, xaositek said:

For anyone curious - test/beta builds are still happening - 6.12.0-rc2.11 just came out

 

Waiting for the official release... I'm stuck with a white screen after login into the WebGUI. Restarting Nginx and Php doesn't change a thing (error 500). 🥲

[Kilrah]

3 hours ago, gyto6 said:

I'm stuck with a white screen after login into the WebGUI

You didn't read the notes that mention the list of incompatible plugins that need to be removed/installed beta versions of.

[gyto6]

12 minutes ago, Kilrah said:

You didn't read the notes that mention the list of incompatible plugins that need to be removed/installed beta versions of.

I did at the time and remove all of them, the white screen has appeared suddenly after importing my ZFS Pool and was never able to access it ever since.

Whatever, I abandoned the idea to test the RC release.

 

Edited April 12 by gyto6

[jonathanselye]

Kernel 6.2 is already stable even Ubuntu's next version is going to release with it as its kernel, and it has full support for intel arc, can we possibly see this on the stable release Soon™ or possibly next RC?

Thanks!

[gyto6]

2 hours ago, jonathanselye said:

Kernel 6.2 is already stable even Ubuntu's next version is going to release with it as its kernel, and it has full support for intel arc, can we possibly see this on the stable release Soon™ or possibly next RC?

Thanks!

Only a fortune teller can answer this question. Whatever it'll come, soon or later.
I think that Limetech's team has enough work now, and finishing the new Unraid release is above the new kernel, which might be unstable with their solution.

[JorgeB]

2 hours ago, jonathanselye said:

Kernel 6.2 is already stable

OpenZFS is currently only compatible with kernel 6.1, and since Unraid now comes with zfs it needs to wait for an officially compatible release.

[Lolight]

6.12.0-rc3 is Now Available

 

https://unraid.net/blog/6-12-0-rc3

 

 

[gyto6]

3 hours ago, Lolight said:

6.12.0-rc3 is Now Available

 

https://unraid.net/blog/6-12-0-rc3

 

 

 

[Nano]

On 3/24/2023 at 7:31 PM, JorgeB said:

 

 

There are advantages and disadvantages for both:

 

array good:

• even if you lose more disks than parity can emulate the data on the remaining good disks can still be read
• any filesystem corruption will only affect that particular disk
• you can fully utilize disks of different capacities and if you upgrade just one disk its capacity can be fully used.
• you can add/remove a single disk or more at any time

 

array bad:

• performance
• no zfs self healing

 

Pools are basically the opposite.

 

pool good:

• performance
• zfs self healing

 

pool bad:

• if you lose more disks than the pool redundancy can recover from the complete pool is gone
• if the pool filesystem gets corrupted you can lose the whole pool, and while this is rare with zfs it can happen
• you can use disks of different capacity in raidz but it will only use the capacity of the smallest one, only when all pool disks are upgraded to a larger same size can the pool be expanded
• you cannot expand a raidz pool with a single disk (at least not for now), you can add another vdev of the same width, say for example you have a 4 disk raidz1 pool, you can add another 4 disks in raidz1 to expand it
• you cannot remove one or more disks (including a complete vdev) from a raidz pool, mirrors are more flexible but I would guess most are interested in using raidz with zfs

 

 

I'm sure I forgot some but these should be the main ones.

Does ZFS keep disks span up for longer, I do like how my disks are mostly sleeping as 99% of constant function is on Cache currently

Edited April 15 by Nano

[Kilrah]

12 hours ago, Nano said:

Does ZFS keep disks span up for longer, I do like how my disks are mostly sleeping as 99% of constant function is on Cache currently

Should behave just the same in the array. Obviously in a multi-drive pool if an access is made to it then all of the pool's drives need to spin up. 

[gyto6]

On 4/12/2023 at 6:39 PM, JorgeB said:

OpenZFS is currently only compatible with kernel 6.1, and since Unraid now comes with zfs it needs to wait for an officially compatible release.

@jonathanselye
OpenZFS 2.1.10 now supports Linux Kernel 6.2 : https://github.com/openzfs/zfs/releases/tag/zfs-2.1.10

[SimonF]

17 minutes ago, gyto6 said:

@jonathanselye
OpenZFS 2.1.10 now supports Linux Kernel 6.2 : https://github.com/openzfs/zfs/releases/tag/zfs-2.1.10

Unlikely for kernel to be bumped to 6.2 during rc phase.

[gyto6]

Just now, SimonF said:

Unlikely for kernel to be bumped to 6.2 during rc phase.

Absolutely, It's not worthy to install the new kernel only for ZFS users to use the latest revision.
Unraid's stability is above all.

[Nano]

@Kilrah

so I think this would cause more power draw, if you have 3 media files across 3 disks without ZFS, only 1 disk spins up if I access 1 of the files where as in the ZFS Pool all 3 disks spin up. If I understand correctly.

Edited April 19 by Nano