Giving a Core Storage logical volume to ZEVO

Moderators: jhartley, MSR734, nola

Re: Giving a Core Storage logical volume to ZEVO

Post by raattgift » Fri Apr 05, 2013 10:05 am

single lvg is possible, just the concat seems not to work


PV, not LVG.

What disk block size does your disk2 report ? (diskutil info disk2). Is it the same as disk1?
raattgift Offline


 
Posts: 98
Joined: Mon Sep 24, 2012 11:18 pm

Re: Giving a Core Storage logical volume to ZEVO

Post by mnos3c » Fri Apr 05, 2013 4:45 pm

raattgift wrote:
single lvg is possible, just the concat seems not to work


PV, not LVG.

What disk block size does your disk2 report ? (diskutil info disk2). Is it the same as disk1?



1) PV=?
2) does it matter? I can't verify now because I don't have disks with me atm. I will but in meantime I'm curios about why it's important..

I remember that I've tested with 2x1tb 4k advanced format disks (1xsamsung, 1xhgst) and with 1x1tb and 1x4gb usb pen.
mnos3c Offline


 
Posts: 33
Joined: Wed Dec 26, 2012 6:40 am

Re: Giving a Core Storage logical volume to ZEVO

Post by raattgift » Fri Apr 05, 2013 7:10 pm

1) Physical Volume. PVs are described in "man diskutil".

2) It matters for 10.7. 10.8 and its updates have introduced many improvements to Core Storage. No they are not publicly documented in any useful detail. :-(
raattgift Offline


 
Posts: 98
Joined: Mon Sep 24, 2012 11:18 pm

Re: Giving a Core Storage logical volume to ZEVO

Post by mnos3c » Fri Apr 05, 2013 7:21 pm

raattgift wrote:1) Physical Volume. PVs are described in "man diskutil".

2) It matters for 10.7. 10.8 and its updates have introduced many improvements to Core Storage. No they are not publicly documented in any useful detail. :-(



With my big surprise my internal disk (1x1tb hgst) shows the following:

Code: Select all
   Device Block Size:        512 Bytes


But it's a 4k AF disk! It's also bold written on it's paper label (on 1tb samsung is not written but in vendor's specs is written).
Osx can't correctly handle this disk? I used ashif command when formatting disks..I will try without it. Any advice?
mnos3c Offline


 
Posts: 33
Joined: Wed Dec 26, 2012 6:40 am

Re: Giving a Core Storage logical volume to ZEVO

Post by mnos3c » Fri Apr 05, 2013 9:26 pm

Well on 10.8.3 I am able to create a LVG with 2 disks concatenated.

Code: Select all
diskutil list
...
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 GB     disk2
   1:          Apple_CoreStorage                         1.0 GB     disk2s1
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *2.0 GB     disk3
   1:          Apple_CoreStorage                         1.9 GB     disk3s1
   2:                 Apple_Boot Boot OS X               134.2 MB   disk3s2


Code: Select all
diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 457EEAA6-4A11-43FD-B8A9-1194D0BD21CA
    =========================================================
    Name:         TestLVG
    Status:       Online
    Size:         2887696384 B (2.9 GB)
    Free Space:   2283700224 B (2.3 GB)
    |
    +-< Physical Volume 56FD29BC-DA91-4E55-818B-A72FB8547173
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s1
    |   Status:   Online
    |   Size:     1019174912 B (1.0 GB)
    |
    +-< Physical Volume 3C45CE98-7233-4329-8994-F83BED6680B5
        ----------------------------------------------------
        Index:    1
        Disk:     disk3s1
        Status:   Online
        Size:     1868521472 B (1.9 GB)


Now, how can I give this volume to ZEVO?
I tryied this command:
Code: Select all
diskutil coreStorage createVolume 457EEAA6-4A11-43FD-B8A9-1194D0BD21CA zfs test 100%

Code: Select all
Error creating CoreStorage Logical Volume: The given file system is not supported on Core Storage (-69756)


But as you can read it gives error. 10.8.3 fresh install with ZEVO 1.1.1 on it from start (no previous install of nothing like maczfs, etc).
mnos3c Offline


 
Posts: 33
Joined: Wed Dec 26, 2012 6:40 am

Link

Post by grahamperrin » Sat Apr 06, 2013 3:31 am

Operating systems such as 10.7.5 and 10.8.3 are limited.

Please see the Ask Different (Stack Exchange) answer linked from the opening post:


If, say, you don't need encryption:

  • skip, or vary from, the parts of the answer that don't apply.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

OT from ZEVO, support for Fusion Drive

Post by grahamperrin » Sat Apr 06, 2013 12:56 pm

grahamperrin wrote:
raattgift wrote:… the composite disk is just a concatenation, though; except in one special case, writes will go to the first physical volume until that fills, then to the second physical volume. (the special case is if the first PV is a solid state disk and your particular kernel supports fusion drives; not all 10.8.2 or 10.8.3 kernels do).


That's most useful. Do we have authoritative references? …


I found OS X 10.8.3 Now Offers Fusion Drive Possibilities For Non-Fusion Drive Equipped Macs | Other World Computing Blog (highlights) – no mention of the kernel but it makes sense, and it seems consistent with raattgift's advice.

When Fusion Drive was first announced, I recall Apple writing about a special Disk Utility, or words to that effect. In build numbers etc. I never found evidence of that specialism, so maybe the description of "Disk Utility" was a dumbing down at the time.
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: Giving a Core Storage logical volume to ZEVO

Post by raattgift » Mon Apr 08, 2013 6:10 am

There was indeed a special Disk Utility.app and some associated Framework and /usr/libexec files that were delivered with 10.8.2 and updates for Macs that supported Fusion Drive and some updates to "Recovery HD" data, as the tools for all other versions of 10.8.2 (no support for Fusion Drive before that) did not know how to set up CS for a Fusion Drive in the event the LVG were deleted. The code was merged in 10.8.3, again except for Macs for which Core Fusion is not supported.

The definitive test for whether or not the (Wr|Rd)BgMigrCS vfs activity will ever happen (other than watching for them via fs_usage -w) is to look for an appropriate startup-time kernel message like this one:

"Apr 8 09:45:51 localhost kernel[0]: thr 0xffffff802f16e000 Composite Disk alg="bloomclock" unit_nbytes=131072"

No "Composite Disk alg" kernel message, no Background Migration thread, no "Fusion Drive" in the sense of no automatic usage-driven movement of Chunks among the components of the Composite Disk, period. (There will be movement of internal-to-CS metadata for a variety of reasons, but they use (Rd|Wr)Meta and (Rd|Wr)MetaCS vfs calls.

There remain kernel differences in 10.8.3 that will lead to boot failures when moving a boot volume from a CS-capable Mac to a non-CS-capable Mac. It is NOT just the CS stuff which at the root of this, however.
raattgift Offline


 
Posts: 98
Joined: Mon Sep 24, 2012 11:18 pm

Previous

Return to General Discussion

Who is online

Users browsing this forum: ilovezfs and 0 guests

cron