PP32 R8 Raid10 - single Logical Drive with multiple partitions, or multiple LD

  • 27 Views
  • Last Post 4 days ago
Chris Brown posted this 6 days ago

After the ongoing inabilty to determine accurate size allocations, and the LV being formatted as APFS, I bit the bullet and spent a couple of days moving data off the Pegasus to available/newly aquired for the process devices

- barrel of fun

 

updated firmware

created new array

first created x5 LV, and formatted each under DiskUtility as  Mac OS Extended (journaled), GUID partition map

 

thought about this for a bit, then thought to try one LV with multiple partitions

deleted and created new array

created one LV

created x5 partitions on that one LV

 

Both approaches create x5 mounted volumes, which is a bit of a pain re the resultant desktop clutter

 

So given the Pegasus is used for deep/archival storage and defacto backup, my question is, is there any overall advantage to either

1) one LV with multiple partitions

or

2) multiple LV, one patition

 

 

I'm thinking one LV with multiple partitions has some advantage when doing backups with CarbonCopyCloner, and searches... as the index will be smaller ( targeting one smaller volume/partition) rather than one much bigger single LV index

 

I see the effect of smaller indexes daily - a particular directory of 200,000 first level folders each names as a UUID value, doing a find, or a get info, on that takes forever (evevn on my mac mini m4 pro) . The archival content, going back years, hardly ever gets hit.

general thinking is more smaller is more manageble

leave the RaId to the Pegasus, leave the file management to the file system ( aka partition)

 

Either way, pity about all those mount points

 

 

 

 

 

 

 

 

 

 

 

R P posted this 4 days ago

Hi Chris,

So given the Pegasus is used for deep/archival storage and defacto backup, my question is, is there any overall advantage to either

1) one LV with multiple partitions

or

2) multiple LV, one patition

In the Pegasus you create an array, a set of disks, upon which you create 1 or more LUNs.

So it looks like these are the options.

1. Create 1 LUN and use disk utility to create multiple partitions
2. Create multiple LUNs in a disk array and put a filesystem on each.

In 1. above macOS is managing the partitions while in 2. above macOS is managing the partitions while the Pegasus is managing the LUNs.

But in either case the limiting factor seems to be seek time as CCC accesses each of thousand of small files, it has to seek to track 0 for each file to find out where it is, so there should be a lot of long seeks.

It's hard to say, but it will probably be about the same either way.

 

 

Search
Categories
Close