Logical Volume is non-contiguous

I'm having problems creating database files on a certain logical volume. It is configured non-contiguous. Does this matter?

connect / as SYSDBA
set echo on
spool /u02/app/oracle/admin/mmstus/create/crt_mmstus.log
startup nomount pfile="$ORACLE_HOME/dbs/initMMSTUS.ora";
CREATE DATABASE MMSTUS
MAXINSTANCES 1
MAXLOGHISTORY 1
MAXLOGFILES 255
MAXLOGMEMBERS 5
MAXDATAFILES 1024
DATAFILE '/u03/oradata/MMSTUS/system01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
EXTENT MANAGEMENT LOCAL
DEFAULT TEMPORARY TABLESPACE TEMP
TEMPFILE '/u03/oradata/MMSTUS/temp01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
UNDO TABLESPACE "UNDOTBS1"
DATAFILE '/u03/oradata/MMSTUS/undotbs01.dbf' SIZE 2048M
AUTOEXTEND ON NEXT 1024M MAXSIZE 4096M
CHARACTER SET AL32UTF8
NATIONAL CHARACTER SET AL16UTF16
LOGFILE GROUP 1 ('/u02/oralog/MMSTUS/mmstus_redo1_1A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_1B.log') SIZE 100M ,
GROUP 2 ('/u02/oralog/MMSTUS/mmstus_redo1_2A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_2B.log') SIZE 100M ,
GROUP 3 ('/u02/oralog/MMSTUS/mmstus_redo1_3A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_3B.log') SIZE 100M ,
GROUP 4 ('/u02/oralog/MMSTUS/mmstus_redo1_4A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_4B.log') SIZE 100M ,
GROUP 5 ('/u02/oralog/MMSTUS/mmstus_redo1_5A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_5B.log') SIZE 100M ,
GROUP 6 ('/u02/oralog/MMSTUS/mmstus_redo1_6A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_6B.log') SIZE 100M ,
GROUP 7 ('/u02/oralog/MMSTUS/mmstus_redo1_7A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_7B.log') SIZE 100M ,
GROUP 8 ('/u02/oralog/MMSTUS/mmstus_redo1_8A.log',
'/u03/oralog/MMSTUS/mmstus_redo1_8B.log') SIZE 100M ;
spool off
exit;
The init.ora file has db_name=MMSTUS

Similar Messages

Extend System Simple Volume to Non-Contiguous Unallocated Space

Hi:
I have a Windows Server 2008 R2 virtual machine for which I need to extend the system simple volume on a dynamic disk to non-contiguous unallocated space. I realize 2008 Disk Manager and diskpart cannot accomplish this but that some 3rd party tools
can get the job done. Does anyone recommend a specific 3rd party application that they've used for this purpose successfully, or any horror stories/products to stay away from?
Thank you!
Bob Herman IT Tropolis

Hi,
Microsoft does not provide third party software, you can backup the partition which is contiguous with system simple volume and delete it. Then, merge unallocated space to the system simple volume with Disk Management snap-in.
Best Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Error: -69774: Couldn't bring the new Core Storage Logical Volume online

Hi,
I have a filevault encrypted drive (750GB).
I first noticed a problem when it prompted my for the FileVault passphrase (which I had stored in my keychain) and entering the correct passphrase resulted in the typical "error" response (the sideways "bouncing" entry field) asking me for the passphrase again.
So I get a list of the corestorage to get the UUID of the encrypted volume:
>diskutil corestorage list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group ********-****-****-****-************
    =========================================================
    Name:         750GB APPLE HDD
    Status:       Online
    Size:         749812400128 B (749.8 GB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume ********-****-****-****-************
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s2
    |   Status:   Online
    |   Size:     749812400128 B (749.8 GB)
    |
    +-> Logical Volume Family ********-****-****-****-************
        Encryption Status:       Locked
        Encryption Type:         AES-XTS
        Conversion Status:       Complete
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            Yes
        Passphrase Required:     Yes
        |
        +-> Logical Volume ********-****-****-****-************
            Disk:                  -none-
            Status:                Locked
            Size (Total):          749493624832 B (749.5 GB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               750GB APPLE HDD
            Content Hint:          Apple_HFS
Using command line I get the following response:
>diskutil corestorage unlockvolume UUID -stdinpassphrase
{UUID being the one of the last Logical Volume named "750GB APPLE HDD"}
Passphrase:
Started CoreStorage operation
Logical Volume successfully unlocked
Error: -69774: Couldn't bring the new Core Storage Logical Volume online
next I try:
>diskutil corestorage revert UUID -stdinpassphrase
Passphrase:
Started CoreStorage operation on disk3
Error: -69741: The target disk isn't eligible for reversion because it wasn't created by conversion or it is not part of a simple setup of exactly one logical and one physical volume
and then:
>diskutil corestorage unlockvolume UUID -stdinpassphrase
Passphrase:
Error beginning CoreStorage Logical Volume unlock: The target Core Storage volume is not locked (-69748)
looking at the kernel log I see the following interesting entries:
08.12.13 15:32:47,000 kernel[0]: CoreStorage: fsck_cs has finished for group "UUID" with status 0x00
08.12.13 15:32:47,000 kernel[0]: CoreStorageFamily::unlockVEKs() failed to unwrap the vek, status = e00002bc
08.12.13 15:33:10,000 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "750GB APPLE HDD" (UUID), pv UUID-of-Physical-Volume, near LV byte offset = 0.
08.12.13 15:34:51,000 kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002d9 detected for LVG "750GB APPLE HDD" (UUID), pv UUID-of-Physical-Volume, near LV byte offset = 0.
BTW: after a while I also hear a single clicking sound (head jumping back on drive) so I am not sure if it might be a physical disk failure.
Any ideas anyone?

Also, I've tried Terminal command: diskutil corestorage revert UUID -stdinpassphrase which returned "Error: -69854: A disk with a mount point is required"
Also, I've tried Terminal command: diskutil corestorage changeVolumePassword UUID -newpassphrase which returned "Error beginning CoreStorage Logical Volume unlock: The target Core Storage volume is not encrypted (-69755)"

Logical Volume Group and Logical Partition not matching up in free space

I was dual booting Windows 7 and Mountain Lion. Through Disk Utility, I removed the Windows 7 Partition and expanded the HFS+ partition to encompass the entire hard drive. However, the Logical Volume Group does not think that I have that extra free space. The main problem is that I cannot resize my partition. I am wanting to dual boot Ubuntu with this. Any ideas? Any help is appreciated. I will post some screenshots with the details. Furthermore, here are some terminal commands I ran: /dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 249.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS MAC OS X *248.9 GB disk1 Filesystem 1024-blocks Used Available Capacity iused ifree %iused Mounted on
/dev/disk1 243031288 153028624 89746664 64% 38321154 22436666 63% /
devfs 189 189 0 100% 655 0 100% /dev
map -hosts 0 0 0 100% 0 0 100% /net
map auto_home 0 0 0 100% 0 0 100% /home CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 52A4D825-B134-4C33-AC8B-39A02BA30522
=========================================================
Name: MAC OS X
Size: 249199587328 B (249.2 GB)
Free Space: 16777216 B (16.8 MB)
|
+-< Physical Volume 6D7A0A36-1D86-4A30-8EB5-755D375369D9
| ----------------------------------------------------
| Index: 0
| Disk: disk0s2
| Status: Online
| Size: 249199587328 B (249.2 GB)
|
+-> Logical Volume Family FDC4568F-4E25-46AB-885A-CBA6287309B6
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: Converting
Conversion Direction: backward
Has Encrypted Extents: Yes
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume BB2662B7-58F3-401C-B889-F264D79E68B4
Disk: disk1
Status: Online
Size (Total): 248864038912 B (248.9 GB)
Size (Converted): 130367356928 B (130.4 GB)
Revertible: Yes (unlock and decryption required)
LV Name: MAC OS X
Volume Name: MAC OS X
Content Hint: Apple_HFS

Here is another try via the command line:
dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
Started CoreStorage operation
Checking file system
Performing live verification
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Incorrect block count for file 2012.12.11.asl
(It should be 390 instead of 195)
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Invalid volume free block count
(It should be 21713521 instead of 21713716)
The volume MAC OS X was found corrupt and needs to be repaired
Error: -69845: File system verify or repair failed

Logical volume is 'not' in filesystem?

Hi,
I have installed arch linux on a PogoPlug B01, and have used lvm to configure two HDDs into a software-raid 0 logical volume, as such:
lvdisplay
--- Logical volume ---
LV Path /dev/VolGroup00/lvolpink
LV Name lvolpink
VG Name VolGroup00
LV UUID pchxXD-c2j4-phRy-v5q5-3Bfd-R1Vy-TsAete
LV Write Access read/write
LV Creation host, time ,
LV Status available
# open 0
LV Size 3.64 TiB
Current LE 953862
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
However, the LV Path does not exist, and the lv doesn't show up in /dev/mapper. The only thing within that directory is a 'control' directory. If I add the LV UUID to /etc/fstab and mount -a, I get the usual 'special device does not exist' error. Does anyone know what may be causing this?
Thanks,
Chris

Hi,
If possible , could you buy without catalogue just to eliminate a business case.
If for non catalogue purchase , the error still occurs thne you probably have a customizing error.
If it works, then we have to focus on the catalog flow side.
Kind regards,
Yann

Failed to revert logical volume group while merging partition

Hi All,
Previously, on my macbook pro, I partitioned my disk for win7 for my dual operation system and only left 120 GB for OS, now I want to delete win7 and return disk space to OS. Currently my OS is yosemite.
I have already deleted disk space for win7 and merged it back to disk0s3. And, I had a problem to merge disk0s2 with disk0s3.
I was told it is because I need to revet my Logical Volume Group. I am blocked at reverting it.
This is my disk info:
rescomp-14-251133:~ rico$ diskutil list; diskutil cs list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         119.3 GB   disk0s2
   3:                  Apple_HFS Recovery HD             380.6 GB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *119.0 GB   disk1
                                 Logical Volume on disk0s2
                                 CC457129-6FE9-41A0-B0D2-F547F21A7555
                                 Unencrypted
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group F454017F-C531-43BA-B270-E2058E05BFF4
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         119290187776 B (119.3 GB)
    Free Space:   4096 B (4.1 KB)
    |
    +-< Physical Volume AC7A2748-0DA1-49D6-B50C-30348838760E
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     119290187776 B (119.3 GB)
    |
    +-> Logical Volume Family 4B7E6277-69BC-475A-BBB7-7A94D6434D9E
        Encryption Status:       Unlocked
        Encryption Type:         AES-XTS
        Conversion Status:       Converting
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume CC457129-6FE9-41A0-B0D2-F547F21A7555
            Disk:                  disk1
            Status:                Online
            Size (Total):          118954639360 B (119.0 GB)
            Conversion Progress:   -none-
            Revertible:            Yes (unlock and decryption required)
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
when I type unlock:
rescomp-14-251133:~ rico$ diskutil corestorage unlockVolume CC457129-6FE9-41A0-B0D2-F547F21A7555 -stdinpassphrase
CC457129-6FE9-41A0-B0D2-F547F21A7555 is already unlocked and is attached as disk1
It is already unlocked
then, I tried revert it
rescomp-14-251133:~ rico$ diskutil coreStorage revert CC457129-6FE9-41A0-B0D2-F547F21A7555
Passphrase:
Started CoreStorage operation on disk1 Macintosh HD
Error: -69750: Unable to modify a FileVault context
Does anyone how I can revert it, then merge disk0s2 and disk0s3

Here is another try via the command line:
dhcp-10-201-238-248:~ KyleWLawrence$ diskutil coreStorage resizeVolume BB2662B7-58F3-401C-B889-F264D79E68B4 210g
Started CoreStorage operation
Checking file system
Performing live verification
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Incorrect block count for file 2012.12.11.asl
(It should be 390 instead of 195)
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
Invalid volume free block count
(It should be 21713521 instead of 21713716)
The volume MAC OS X was found corrupt and needs to be repaired
Error: -69845: File system verify or repair failed

10g ASM on Logical Volumes vs. Raw devices and SAN Virtualization

We are looking at setting up our standards for Oracle 10g non-rac systems. We are looking at the value of Oracle ASM in our environment.
As per the official Oracle documentation, raw devices are preferred to using Logical Volumes when using ASM.
From here: http://download.oracle.com/docs/cd/B19306_01/server.102/b15658/appa_aix.htm#sthr
ef723
"Note: Do not add logical volumes to Automatic Storage Management disk groups. Automatic Storage Management works best when you add raw disk devices to disk groups. If you are using Automatic Storage Management, then do not use LVM for striping. Automatic Storage Management implements striping and mirroring."
Also, as per Metalink note 452924.1:
"10) Avoid using a Logical Volume Manager (LVM) because an LVM would be redundant."
The issue is: if we use raw disk devices presented to ASM, the disks don't show up as used in the unix/AIX system tools (i.e. smit, lspv, etc.). Hence, when looking for raw devices on the system to add to filesystems/volume groups/etc., it's highly possible that a UNIX admin will grab a raw device that is already in use by Oracle ASM.
Additionally, we are using a an IBM DS8300 SAN with IBM SAN Volume Controller (SVC) in front of it. Hence, we already have storage virtualization and I/O balancing at the SAN/hardware level.
I'm looking for a little clarification to the following questions, as my understanding of their responses seem to confict:
QUESTION #1: Can anyone clarify/provide additional detail as to why Logical volumes are not preferred when using Oracle ASM? Does the argument still hold in a SAN Virtualized environment?
QUESTION #2: Does virtualization at the software level (ASM) make sense in our environment? As we already have I/O balancing provided at the hardware level via our SVC, what do we gain by adding yet another level of I/O balancing at the ASM level? Or as in the
arguments the Oracle documentation makes against using Lvm, is this an unnecessary redundant striping (double-striped or in our case triple-striped/plaid)?
QUESTION #3: So does SAN Virtualization conflict or compliment the virtualization provided by ASM?

After more research/discussions/SR's, I've come to the following conclusion.
Basically, in an intelligent storage environment (i.e. SVC), you're not getting a 100% bang for the buck by using ASM. Which is the cat's meow in a commodity hardware/unintelligent storage environment.
Using ASM in a SVC environment potentially wastes CPU cycles having ASM balance i/o that is already balanced on the backend (sure if you shuffle a deck of cards that are already shuffled you're not doing any harm, but if they're already shuffled - then why are you shuffling them again??).
That being said, there may still be some value for using ASM from the standpoint of storage management for multiple instances on a server. For example, one could better minimize space wastage by being able to share a "pool" of storage between mulitiple instances, rather than having to manage space on an instance-by-instance (or filesystem by filesystem) level.
Also, in the case of having a unfriendly OS where one is unable to dynamically grow a filesystem (i.e. database outage required), there would be a definite benefit provided by ASM in being able to dynamically allocate disks to the "pool". Of course, with most higher-end end systems, dynamic filesystem growth is pretty much a given.
In the case of RAC, regardless of the backend, ASM with raw is a no-brainer.
In the case of a standalone instance, it's a judgement call. My vote in the case of intelligent storage where one could dynamically grow filesystems, would be to keep ASM out of the picture.
Your vote may be different....just make sure you're putting in a solution to a problem and not a solution that's looking for a problem(s).
And there's the whole culture of IT thing as well (i.e. do your storage guys know what you're doing and vice versa).....which can destroy any technological solution, regardless of how great it is.

SE3511 - recovering logical volumes

Hi ,
I have a SE3511 array with one controller array and a JBOD both are fully populated with 400GB disks. There is one each logical drives(RAID5) configured on both controller array and JBOD. Each logical drives were divided into two logical volumes of equal size. SO I had 4 logical volumes total. After doing a physical move of the array to different location, I had some problems witht the array. When I checked the configuration, i could see all the logical volumes are disappeared, but still the logical drives are there. Unfortunately I didn't take a configuration backp of the styorage. But I know the size of the logical volumes.
Can any body help how to recover the lost logical volumes or create the logical volumes without losing data.
Thanks
Babu

Found the following:-
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ls.htm#sthref1308
Oracle® Data Guard Concepts and Administration
10g Release 2 (10.2)
Part Number B14239-04
Managing A Logical Standby Database -- 9.5.4
Indicates that the Logical Standby can recover through an OPEN RESETLOGS if its running in flashback database mode.
Not sure what the impact of this is on non-guarded components - could be that if it flashes the logical back too that it loses all the non-guarded components

Corrupt Root Logical Volume

Hey Folks,
I'm having a bit of a problem with the Root Logical Volume / Volume Group on one of our Servers (OEL 4 - Release 7 running on Oracle VM 2.1.2). One of our SAN Administrators pulled the disk from the system by accident, and has since re-presented it to the server but now when it boots I'm getting errors on the Root Logical Volume.
It boots in to maintenance mode and I've tried fsck'ing the root file system but it gives errors about the first SuperBlock...
"Attempt to read block from filesystem resulted in short read while trying to open /dev/VolGroup00/LogVol00
Could this be a zero-length partition? "
I've tried specifying the next SuperBlock and the e2fsck runs through repairing corrupt inodes, but it doesn't make a difference, I still get errors on bootup. Any other LVM commands give an error to say that 'File Descriptor XX not closed'.
I've booted from an OS DVD in to Rescue Mode and it mounts the Volume Groups and I can still see the files are present.
Does anyone know of anything I can do? Are their commands I can run in Rescue Mode to fix corrupted file systems? I'm off to do some googling on the subject but if anyone could offer advice it would be much appreciated.
Thanks
James

Please mind any corruptions inside the filesystem can occur. You should check that in two stages:
-Non-oracle
All operating system tools use normal, buffered IO. (that I am aware of, please correct me if somebody has seen something different)
This means that any file modifications (user-imposed, thus modified configuration files, and system imposed, like installing binaries) are done in memory, and eventually flushed to disk (by a process called 'pdflush'). When a disk is pulled, there is a chance not all modifications are already flushed to disk, thus will be corrupt.
-Oracle
This is the same for the oracle database files, with the exception of databases using DIO, direct IO. Direct IO is enabled if the database parameter 'filesystemio_options' is set to 'direct' or 'setall'. Direct IO bypasses the operating system buffercache and does IO (reading and writing) directly from the blockdevice, instead of asking the operating system for the block in normal mode, which caches the requested block(s) in the operating system/linux buffercache.
That is why normal/cached IO also is said to do 'double buffering', because there are two cache's ('buffers') involved.
-Okay, but it's journalled, isn't it?
Eh, yes.
But it depends on the type of journalling. Journalling might not be what you expect it to be.
Most filesystems, including NTFS and default ext3, only journal metadata transactions. Metadata transactions mean that only changes to the structure of the filesystem are journalled, not data-transactions.
Please mind that it is possible for ext3 to journal all modifications instead of only meta-data with the 'data=journal' mount option.

[solved] Filesystem check fail - Cannot access LVM Logical Volumes

I am getting a "File System Check Failed"on startup, I recently did a full system upgrade but I'm not entirely sure that the cause of the issue as I don't reboot very often.
I get the error right before this line is echo'ed out:
/dev/mapper/Arch_LVM-Root:
The super block could not be read or does not describe a correct ext2 filesystem...
this is odd because the only ext2 filesystem I have is on an non-LVM boot partition...
I can log-in and mount / as read/write and I can activate LVM with
modprobe dm-mod
and
vgchange -ay Arch_LVM
and they show up in lvdisplay but their status is "NOT available"
I just need to mount these logical volumes so I can retrieve some personal data in my home directory, I am also hesitant to use LVM again if I can't retrieve my data.
any suggestions?
Last edited by action_owl (2010-08-15 02:15:58)

I just popped in the install disk and was able to mount and access the LVM groups as expected, something must have been wonky with my filesystem

Unable to encrypt the Core Storage logical volume

What's going on here?
dmd@lumen ~ $ diskutil cs encryptVolume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
New passphrase for existing volume:
Confirm new passphrase:
Started CoreStorage operation on disk3 megafauna
Scheduling encryption of Core Storage Logical Volume
Error: -69694: Unable to encrypt the Core Storage logical volume
Underlying error: -536870212: Unknown error: -536870212
Here is the relevant volume information:
    +-> Logical Volume Family D556AA79-22D7-49A4-8ADD-8028F0646060
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
            Disk:               disk3
            Status:             Online
            Size (Total):       1149639159808 B (1.1 TB)
            Size (Converted):   -none-
            Revertible:         No
            LV Name:            megafauna
            Volume Name:        megafauna
            Content Hint:       Apple_HFS

Huh. Well, maybe that's why.
It was certainly happy enough to let me MAKE a LVG with multiple LVFs. Do you mean it just doesn't support encryption on a LVG with multiple LVFs?
+-- Logical Volume Group 736244AD-CDF2-4846-9343-2E2A4D487434
    =========================================================
    Name:         seagate1.5TDiskLVG
    Status:       Online
    Size:         1499957936128 B (1.5 TB)
    Free Space:   0 B (0 B)
    |
    +-< Physical Volume E3B2A090-0BD7-433B-BDEA-7B19174FBAB1
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk2s2
    |   Status:   Online
    |   Size:     1499957936128 B (1.5 TB)
    |
    +-> Logical Volume Family 55E5E43A-8EC9-4760-8F42-1B4AF17F3184
    |   ----------------------------------------------------------
    |   Encryption Status:       Unlocked
    |   Encryption Type:         AES-XTS
    |   Conversion Status:       Converting
    |   Conversion Direction:    forward
    |   Has Encrypted Extents:   Yes
    |   Fully Secure:            No
    |   Passphrase Required:     Yes
    |   |
    |   +-> Logical Volume E0C47F65-A93B-4C33-B915-F33760A75716
    |       ---------------------------------------------------
    |       Disk:               disk4
    |       Status:             Online
    |       Size (Total):       350000001024 B (350.0 GB)
    |       Size (Converted):   211705397248 B (211.7 GB)
    |       Revertible:         No
    |       LV Name:            bonzai
    |       Volume Name:        bonzai
    |       Content Hint:       Apple_HFS
    |
    +-> Logical Volume Family D556AA79-22D7-49A4-8ADD-8028F0646060
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume 1C8F9744-6E91-4915-B9E1-6BDA6B4D2A9F
            Disk:               disk3
            Status:             Online
            Size (Total):       1149639159808 B (1.1 TB)
            Size (Converted):   -none-
            Revertible:         No
            LV Name:            megafauna
            Volume Name:        megafauna
            Content Hint:       Apple_HFS

Problem trying to clue non contiguous audio regions

I'm trying to glue together non contiguous audio regions after cutting up loop.
I know I should get a dialogue box telling me that logic will create a new region, but this is not happening and it wont let me glue the region together, is there an option or something to turn this function on?
any help would be great thanks

your problem is most likely that you're trying to do this with apple loops, not normal audio files. you can't use these functions with apple loops, along with others such as fade in/out and crossfade. you'll have to export the selection to a new audio file, or bounce it.

Finding whole mapping from database file - filesystems - logical volume manager - logical partitions

Hello,
Trying to make reverse engeneering of database files and their physical carriers on logical partitions ( fdisk ).
And not able to make whole path from filesystem down to partitions with intermediate logical volumes.
1. select from dba_data_files ...
2. df -k
to get the listing of filesystems
3. vgdisplay
4. lvdisplay
5. cat /proc/partitions
6. fdisk /dev/sda -l
   fdisk /dev/sdb -l
Problem I have is that not able to determine which partitions are consisten in logical volumes. And then which logical volumens are consisted in filesystem.
Thank you for hint or direction.

Hello Wadhah,
Before start the discussion let me explain I am newcommer to Oracle Linux. My genetic with dba experience of Oracle is from IBM UNIX ( AIX 6.1 ) and Oracle 11gr2.
First task is to get the complete picture of one database on Oracle Linux for future maintenance tasks and make database more flexible and
preparing for more intense work:
-adding datafiles,
-optimize/replace archive redolog files on separated filesystem from ORACLE_BASE
- separating auditing log files from $ORACLE_BASE to own filesystem
- separating diag directory on separated file system ( logging, tracing )
- adding/enlarging TEMP ts
- adding/enlarging undo
- enlarging redo for higher transaction rate ( to reduce number of switched per time perceived in alert_SID.log )
- adding online redo and control files mirrors
So in this context try to inspect content of the disk space from the highest logical level in V$, DBA views down to fdisk partitions.
The idea was to go in these steps:
1. select paths of present online redo groups, datafiles, controlfiles, temp, undo
   from V$, dba views
2. For the paths got from the step 1
   locate filesystems and for those filesystems inspect which are on logical volumens and which are directly on partitions.
3. For all used logical volumes locate the logical partitions and their disks /dev/sda, /dev/sdb, ...

Error message when installing Yosemite OS: this core storage operation is not allowed on a sparse logical volume group

I was updating my Macbook Air (i7, 4mb RAM, 256 gb) to Yosemite OS when the process was interrupted. After retry, my computer is showing the following message: "this core storage operation is not allowed on a sparse logical volume group". I tried to restart several times, but the problem goes on with error. It would be my computer damaged?

If you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

Volume encrypt and erase failed; unable to delete core storage logical volume

I was attempting to slowly migrate [MI-***] from early 2013 MBPRO to New iMac 5K w/Ceiling Level components.
Kept going through LONG process and then told me it couldn't create [MBPRO HD Home Username] "Jim" on volume or whatever. NO FileVault enabling/ still skittish from White iMac Encrypting Nightmare days... I don't even know -- I guess it's encrypted on Airport, but not on MBPRO.
Moved over Applications from outside User account fine; anything inside any User account NOT FINE.
Hooked up Thunderbolt cable between two macs and restarted MBPRO in T mode... displaying the lightning BOLT on screen that moves around to reduce Burn-in.
Was able to go onto desktop and use windows to drag n drop 190G of movies over to iMac... wondering how I was going to get all right settings over form FCP...
Bottom Line: I only have 16G left on MBPRO and need to MOVE video editing to be exclusive on 3T Fusion on Maxed out iMac 5K.
> Have concluded through whole process that I just want to clone the MBPRO and then delete most of the Larger Videos from MBPRO to recover some of my 760G SSD back.
So, I grabbed my 2T Airport Extreme and Hooked up the Cat5 LAN port to Cat5 input on back of NEW iMac; Now my MBPRO doesn't have to be locked up for days, because i can use TimeMachine backup to restore or clone the two macs... i hope.
Went into recovery mode and selected sub-Macintosh HD and attempted to erase; Result time after time after time: "Volume Encrypt and Erase failed." Reason: "Unable to delete the Core Storage logical volume." It dismounts it and I have to restart computer to get it back on. Funny thing is I don't have to use R anymore... which by the way, Command+R appears to be same as just plain old R when restarting... why is that?
This has become a "since Christmas" runaround session for me and I am sick of it.
Please help. I would've called Apple Care [and I did last night while driving... just to get advice on direction. I'm usually a pretty savvy PowerUser but this is driving me crazy.] but have to get things done for a meeting tomorrow. Can work on it after hours if someone can advise today on this post.
Thx,
Jim

I have taken some screenshots of the error I get and the state of my HDD in Disk Utility. I did have a weird thing happen after trying to repair using single user mode, where I reopened disk utility and the partitions were NOT greyed out and displayed the correct info concerning space available etc, although after verifying it then reverted back to greyed out with no info.

Logical Volume is non-contiguous

Similar Messages

Maybe you are looking for