Renamed Volumes on Backup LDOM

When we originally created ldoms on the primary we had volume names as such
VDS
NAME VOLUME OPTIONS DEVICE
front1_1vol /dev/rdsk/c6t60060160F180200040BD08CFB982DD11d0s2
front1_2vol /dev/rdsk/c6t60060160F18020008CC29E0ABA82DD11d0s2
front1_3vol /dev/rdsk/c6t60060160F1802000AA228339BA82DD11d0s2
front1_4vol /dev/rdsk/c6t60060160F18020000ECD1E6CBA82DD11d0s2
We stopped the domains copied the images and created the same volumes on another server using
ldm list-constraints -x front > front.xml
we then imported using create
ldm add-domain -i front.xml
Add originally the domains had the same volume names. At some point all the volume names got renamed to something as such. Not sure why they got renamed. The hostnames were changed to ctrlp and ctrls instead of tip1 and tip2.
VDS
NAME VOLUME OPTIONS DEVICE
primary-vds0-vol31 /dev/rdsk/c6t60060160F180200040BD08CFB982DD11d0s2
primary-vds0-vol32 /dev/rdsk/c6t60060160F18020008CC29E0ABA82DD11d0s2
primary-vds0-vol33 /dev/rdsk/c6t60060160F1802000AA228339BA82DD11d0s2
primary-vds0-vol34 /dev/rdsk/c6t60060160F18020000ECD1E6CBA82DD11d0s2
We made changes to 1 VM on the primary and repeated the process with list-constraints and coping the updated image back over to the secondary not knowing these volume names got changed and now when we try and bind we get errors as such
The volume "front1_1vol" does not exist on virtual disk server "primary-vds0".
However the volume is there but with a different name.
Can someone explain why the volume names got changed and is there a way to just rename a volume in the bindings without having to completely delete and reload everything.

Are you using the same Virtual Disk Service name on both server (ie primary-vds0 or just vdso)?
I think the vds names have to be consistent accross servers to do what you want to do.

Similar Messages

  • Server 2008 sp2 freezes during DPM 2010 volume shadow backup

    Hi All,
    We have a hyperv guest server 2008 sp2 that freezes during DPM 2010 volume shadow backup.
    I presume this is when backing up SQL databases. There are no errors in the event logs.
    The sequense of entries in the System event are as follows up until the server freezes.
    1) The DPMRA service entered the running state.
    2) The Volume Shadow Copy service entered the running state. 
    3) DCOM  started the service swprv with arguments "" in order to run the server:
    {65EE1DBA-8FF4-4A58-AC1C-3470EE2F376A}
    4) The Microsoft Software Shadow Copy Provider service entered the running state.
    After this the entries stop and the new entries are from after reboot.                                                               
    You cannot send control-alt-delete or connect to the server in any way.
    Only hard reboot gets it going again.This is the only server this is happening to.
    Please advise if anybody has experienced this and how they resolved.
    Maybe I require a Hotfix.

    This looks similar to what I'm seeing.
    DPM 2010, there's one backup set (for me a file server disk) that every time I try to run the initial replica on it the server hangs and needs to be rebooted by iLO. It doesn't just die suddenly, first the data stream on the backup stops then the OS becomes
    less responsive but there is no resource issue. trying to open event view will cause a few things to lock up then over a few mins the server is complete froze. like the disk drives have been locked.
    Suspecting McAfee, I added in all the exclusions, that didn't help so I added the process exclusions which are done by setting dpmra and csc to low risk and that didn't help either. I could reproduce it just by kicking off a backup for this one file servers
    drive so it's easy to test with.
    Tonight, I had some permissions in EPO to let me stop the scanning completely and disable the on-access scan and for the first time it worked!
    There is definitely an issue between DPM and McAfee beyond what is on MS's web page for AV checks.
    I don't have a workaround yet other than stopping the AV completely... Something to follow up on next week. For the moment I made some progress though.

  • Can anyone help please with my Time Machine, I have been getting the following message The backup disk image "/Volumes/Mac Backup/Stephen Smith's iMac.sparsebundle" is already in use.

    Can anyone help please with my Time Machine, I have been getting the following message The backup disk image “/Volumes/Mac Backup/Stephen Smith’s iMac.sparsebundle” is already in use.

    See > http://pondini.org/TM/C12.html

  • Apple Raid Card - Rename Volume

    The lion install for 10.7.2 apparently fixes the creation of the recover partititon on raid volumes.
    However, it seems to corrupt the name of the volume in my case and I cannot figure out the terminal command to rename the volume back to it's original name of SYSTEM from changed name it creates on install.I'd appreciate if this is expected behavior when it creates multiple partitions on a hardware raid or if this is an error/fault in the way lion alters the disk in anyones experience.
    Any help with the terminal syntax (if it applies) would be greatly appreciated

    Maybe you need to do a full surface scan for bad or weak failing sectors.
    Next time it drops out (or whenever you decide to remove it manually).
    Use Disk Utility to Initialize with Write Zeroes option. This takes several hours.
    If it completes without any error messages at all, it should then be good to use.
    If Bad Blocks are found, they will generally be spared out by this process, and the drive can be good to use for a while, but is likely to fail within 6 months. You should consider moving it to light-duty or occasional use, such as backups.
    Sometimes the Initialization will fail. If the drive is still under warranty, return it to the manufacturer for a refund/replacement. Original Apple drives have a one-year warranty, same as your Mac. Manufacturer warranties are often (but not always) 3 years or more.

  • Purpose of 4 volumes in backup of hana DB

    what are name server index server statistics server,xs engine server in taking backup of hana DB

    The different server processes can have their own persistency (data + log volumes).
    However, all these separate persistencies need to be backed up in sync with the indexserver persistency. That's why they are automatically included in the data backup.
    - Lars

  • Rename Volume in Disk Image

    I'm trying to make a few copies of a home movie DVD a friend made for me. I would like the new discs to have a different title from the generic one.
    However, when I use Disk Utility to "create new image from disk", even when I set it to a read/write image I cannot rename the volume when I mount it. Everywhere I've looked the answer seems to be "mount the disk image, rename the volume, unmount, and you're set, burn away." But I can't rename the volume from Finder, in the 'Get Info' properties window, etc. This is driving me mad, I appreciate any help anyone can offer. Thanks!

    What if anything happens when you try to rename the mounted volume? Is there an error message? Perhaps your drive needs repair:
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    As an afterthought rather than creating the disk image from Disc X instead click on the New Image icon the toolbar, set the required image size and name, select read/write and no encryption. Make the destination the Desktop and click on the Create Image button.
    Message was edited by: Kappy

  • This backup is too large for the backup volume - ridiculous backup size

    I have had big problems with Time Machine today. I have been successfully using it for 2 months now. I have about 30Gb spare on my iMac hard drive (out of 233Gb) and my Time Machine uses 195Gb out of 466Gb available.
    However, today I have lost all my Time Machine history except for one backup made this morning, and I am now getting an error message saying:
    "Time Machine Error
    This backup is too large for the backup volume. The backup requires 161061280.0 GB but only 270.4 GB are available.
    To select a larger volume, or make backup smaller by excluding files, open System Preferences and choose Time Machine"
    Clearly the required backup volume is wrong - that's 161,000.0TB!!!
    The same message has come up 3 times now.
    Can anyone help/advise on what to do next?

    Thanks Peggy,
    I re-indexed Spotlight and ran Time Machine again, but got exactly the same error message and the same massive storage required.
    I've opened Console as you suggested and these are a set of the messages from one back-up attempt yesterday (Console doesn' show anything earlier than 17.32 yesterday - but the problem started earlier than that I believe):
    "16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backup requested by automatic scheduler
    16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Starting standard backup
    16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Event store UUIDs don't match for volume iMac Hard Drive
    16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Starting pre-backup thinning: 157286.40 TB requested (including padding), 270.35 GB available
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] No expired backups exist - deleting oldest backups to make room
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Backup Failed: unable to free 157286.40 TB needed space
    16/01/2008 17:44:49 /System/Library/CoreServices/backupd[326] Backup failed with error: Not enough available disk space on the target volume."

  • Can I rename or move backup files from my Time Capsule?

    I have replalced my Macbook Pro with a new one with the same name. I have backup files on Time Capsule (Time Machine files) that I need to preserve for now, but I want to start backing up the new MB Pro without Time Capsule mixing the old with the new (since they have the same name). So I'd like to move the old files to a different drive or rename them so Time Machine won't use them, but don't want to corrupt them in the process. And if that works, will I still be able to open them to restore select files if needed?
    Really appreciate any advice on this.
    Thanks
    Fred

    You will corrupt your backups if you change any name in your backed up folders. What I recommend you to do is to move your backup files of the old Mac to another external drive, so you do not have them stored on the Time Capsule taking up space for the new Mac > http://support.apple.com/kb/HT5096?viewlocale=en_US&locale=en_US
    Also, see > http://pondini.org/TM/18.html#id21

  • OSB shows nonexistent volumes and backup sections

    lsvol --library lib1
    Inventory of library lib1:
    in 1: unlabeled, barcode DVZ802L4
    in 2: unlabeled, barcode DVZ803L4
    in 3: unlabeled, barcode DVZ804L4
    in 4: unlabeled, barcode DVZ805L4
    in 5: unlabeled, barcode DVZ806L4
    in 6: unlabeled, barcode DVZ807L4
    in 7: unlabeled, barcode DVZ808L4
    in 8: unlabeled, barcode DVZ809L4
    in 9: unlabeled, barcode DVZ810L4
    ob> lsvol --all
    VOID OOID Seq Volume ID Barcode Family Created Attributes
    101 101 1 RMAN-DEFAULT-000002 RMAN-DEFAULT 06/05.08:04 never closes; content manages reuse
    102 102 1 RMAN-DEFAULT-000003 RMAN-DEFAULT 06/05.08:05 never closes; content manages reuse
    103 103 1 RMAN-DEFAULT-000004 RMAN-DEFAULT 06/05.08:07 never closes; content manages reuse
    104 104 1 RMAN-DEFAULT-000005 RMAN-DEFAULT 06/05.08:09 never closes; content manages reuse
    105 105 1 RMAN-DEFAULT-000006 RMAN-DEFAULT 06/05.08:10 never closes; content manages reuse
    106 106 1 RMAN-DEFAULT-000007 RMAN-DEFAULT 06/05.08:25 never closes; content manages reuse
    107 107 1 RMAN-DEFAULT-000008 RMAN-DEFAULT 06/05.08:29 never closes; content manages reuse
    108 108 1 RMAN-DEFAULT-000009 RMAN-DEFAULT 06/05.08:33 never closes; content manages reuse
    109 109 1 RMAN-DEFAULT-000010 RMAN-DEFAULT 06/05.08:34 never closes; content manages reuse
    111 111 1 RMAN-DEFAULT-000011 RMAN-DEFAULT 06/05.14:01 never closes; content manages reuse
    112 112 1 RMAN-DEFAULT-000012 RMAN-DEFAULT 06/05.14:07 never closes; content manages reuse
    113 113 1 RMAN-DEFAULT-000013 RMAN-DEFAULT 06/05.14:12 never closes; content manages reuse
    ob> lspiece
    ob> lssection --long
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    Warning: can't find best volume. - object not found
    ob> lsbackup
    ob> lsbu --long
    ob> lssection long incomplete
    Warning: can't find best volume. - object not found
    Backup section OID: 924
    Containing volume: (unknown)
    Containing volume OID: 177
    File: 1
    Section: 1
    Backup level: 0
    Client: DSI0101
    Encryption: off
    Created: 2008/07/15.11:04
    Warning: can't find best volume. - object not found
    Backup section OID: 938
    Containing volume: (unknown)
    Containing volume OID: 182
    File: 1
    Section: 1
    Backup level: 0
    Client: DSI0101
    Encryption: off
    Created: 2008/07/15.11:06
    Warning: can't find best volume. - object not found
    Backup section OID: 965
    Containing volume: (unknown)
    Containing volume OID: 194
    File: 1
    Section: 1
    Backup level: 0
    Client: DSI0101
    Encryption: off
    Created: 2008/07/15.11:10
    Warning: can't find best volume. - object not found
    Backup section OID: 1009
    Containing volume: (unknown)
    Containing volume OID: 211
    File: 1
    Section: 1
    Backup level: 0
    Client: DSI0101
    Encryption: off
    Created: 2008/07/15.11:17
    ob> rmsection --oid 924
    Error: volume RMAN-1-000016, on which backup section OID 924 resides
    expires at an explicit time. Deleting backup sections it
    contains will have noeffect.
    How to remove volumes: RMAN-DEFAULT-000002 ..RMAN-DEFAULT-000013
    Marcin

    ob> lsvol -al
    Volume OID: 101
    Volume ID: RMAN-DEFAULT-000002
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Rotation policy: rp_mcb
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:04
    Closes: never
    Expires: never; content manages reuse
    Original OID: 101
    Volume OID: 102
    Volume ID: RMAN-DEFAULT-000003
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:05
    Closes: never
    Expires: never; content manages reuse
    Original OID: 102
    Volume OID: 103
    Volume ID: RMAN-DEFAULT-000004
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:07
    Closes: never
    Expires: never; content manages reuse
    Original OID: 103
    Volume OID: 103
    Volume ID: RMAN-DEFAULT-000004
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:07
    Closes: never
    Expires: never; content manages reuse
    Original OID: 103
    Volume OID: 104
    Volume ID: RMAN-DEFAULT-000005
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:09
    Closes: never
    Expires: never; content manages reuse
    Original OID: 104
    Volume OID: 105
    Volume ID: RMAN-DEFAULT-000006
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:10
    Closes: never
    Expires: never; content manages reuse
    Original OID: 105
    Volume OID: 106
    Volume ID: RMAN-DEFAULT-000007
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:25
    Closes: never
    Expires: never; content manages reuse
    Space remaining: 741.3 GB
    Original OID: 106
    Volume OID: 107
    Volume ID: RMAN-DEFAULT-000008
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:29
    Closes: never
    Expires: never; content manages reuse
    Space remaining: 745.4 GB
    Original OID: 107
    Volume OID: 108
    Volume ID: RMAN-DEFAULT-000009
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:33
    Closes: never
    Expires: never; content manages reuse
    Space remaining: 749.4 GB
    Original OID: 108
    Volume OID: 109
    Volume ID: RMAN-DEFAULT-000010
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.08:34
    Closes: never
    Expires: never; content manages reuse
    Space remaining: 740.4 GB
    Original OID: 109
    Volume OID: 111
    Volume ID: RMAN-DEFAULT-000011
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.14:01
    Closes: never
    Expires: never; content manages reuse
    Original OID: 111
    Volume OID: 112
    Volume ID: RMAN-DEFAULT-000012
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.14:07
    Closes: never
    Expires: never; content manages reuse
    Original OID: 112
    Volume OID: 113
    Volume ID: RMAN-DEFAULT-000013
    Volume sequence: 1
    Media family: RMAN-DEFAULT
    Current location: lib1
    Label host: DSI0103
    Created: 2008/06/05.14:12
    Closes: never
    Expires: never; content manages reuse
    Space remaining: 781.5 GB
    Original OID: 113
    ob>

  • Renaming session restore backup doesn't work, how do I restore old session after a crash?

    Computer crashed and Firefox didn't remember my session. It happened a couple weeks ago so I had looked up how to fix and I learned from my mistake and saved the sessionstore.bak file before restarting Firefox. I closed Firefox, deleted sessionstore.js and renamed .bak to js but on startup it still doesn't bring up the restore session. Restore previous on the history tab still greyed out, about:sessionrestore brings up no tabs. I even tried copying that same file and also naming copies as sessionstore-1 & 2. How do I get it to work?

    You can try to restore a previous version of the sessionstore.js or sessionstore.bak file. You need to rename the .bak file to .js to make Firefox see that session.
    right-click: Properties > Previous Versions
    http://windows.microsoft.com/en-US/windows7/Previous-versions-of-files-frequently-asked-questions
    http://kb.mozillazine.org/sessionstore.js
    http://kb.mozillazine.org/Session_Restore
    https://support.mozilla.org/kb/restore-previous-session

  • Time Machine error: The backup disk image "/Volumes/----/----MacBook Pro.sparsebundle" is already in use and resource unavailable?

    I have a MacBook Pro 13" 2010 model running Mountain Lion. I have always been able to use Time Machine with my Time Capsule. Just today I have been receiving the same error message whenever I would back up my computer:
    I removed my name before "MacBook Pro". It takes a long time "Looking for backup disk..." first. The disk I put with the time capsule is called Huge Backup, and in Huge Backup there is my sparsebundle file called "----- MacBook Pro." When I open Finder, open my time capsule, and then open my sparse folder, it should mount a drive where I can see my computer's backups. That doesn't work. Then I get this message:
    I once again removed my name before "MacBook Pro" but I can open my sister's sparsebundle who is running Mountain Lion on the same network and her backups work fine. I have researched this topic and have tried to repair the disk in Disk Utility, remount all the drives, remove the drive and restart the backups, and even restart my computer and the Time Capsule. Nothing worked. It just was working yesterday, but now I get this in the settings along with a caution symbol in my menubar:
    Is there anything I could do to fix this? Reconnecting it in AirPort Utility (5 or 6) didn't work. Also, for some reason, the error renamed Huge Backup to Huge Backup-1 as you can see above and below in the messages. I downloaded the Time Machine Buddy widget and this is the error report I got. I replaced my names or private info with [-----]. By the way, the network is called NDR Network, and the Time Capsule is alled NDR Time Capsule. Here's the error I keep getting:
    Starting manual backup
    Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Disk image already attached: /Volumes/Huge Backup/[-----]'s MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a483e6c0 {MessageParameters=(
    Ejected Time Machine network volume.
    Waiting 60 seconds and trying again.
    Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
    Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Disk image already attached: /Volumes/Huge Backup/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a343d430 {MessageParameters=(
    Ejected Time Machine network volume.
    Waiting 60 seconds and trying again.
    Attempting to mount network destination URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Mounted network destination at mount point: /Volumes/Huge Backup-1 using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
    Disk image already attached: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
    Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a34410c0 {MessageParameters=(
    Ejected Time Machine network volume.
    Giving up after 3 retries.
    Backup failed with error: 31
    [SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
    Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
    Failed to eject Time Machine disk image: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle
    Please help!

    I didn't remove all of my names, so just ignore that...

  • Resize a ldom zdisk volume

    Hi,
    I create a zdisk volume on a T5220 (solaris 11) and installed a solaris10 in a ldom. The zdisk size is 50G.
    After some zone migration inside the ldom, my zdisk is a bit short and I want to increase to 60G.
    I modified the zdisk size where ldom is installed : zfs set volsize=60G dpool/ldom_sol10
    When I check the size on solaris 10 , iostat returns the good new size but the format command see always 50G
    [root@t5222_ldom_sol10]:$ iostat -En
    c0d0             Soft Errors: 0 Transport Errors: 0 Protocol Errors: 0
    Vendor: SUN Product: VDSK Size: 64.42GB <64424509440 bytes>
    [root@t5222_ldom_sol10]:$ format
    Searching for disks...done
     AVAILABLE DISK SELECTIONS:
            0. c0d0 <SUN-DiskImage-50GB cyl 1420 alt 2 hd 96 sec 768>
               /virtual-devices@100/channel-devices@200/disk@0
    Is it possible to resize a zdisk volume where a ldom is installed ?
    Thanks in advance.
    frbo

    R81Z3 wrote:
    In my opinion ZFS likes disks, so using partitions is asking for problems, I am no ZFS expert but ZFS loves memory, and if your system does not have much say less then 8gb you are asking for problems. Also most folks who are serious about ZFS will use ECC memory as that provides data integrity as if your memory does errors ZFS can't fix it but assumes it is correct. Like they say garbage in garbage out. I have had ZFS on a BSD system and it works had no issues but it was a complete disk, and had at least 8gb of memory but I made sure I had backups of important files just to avoid the CRC errors that bad memory can give you.
    You an add and remove pools but ZFS assumes a pool is a disk, and you have to see the documentation for how to do it properly. But I would just use another disk and solve the problem disks are cheap and honestly ZFS loves disks not partitions.
    I have a roughly 2g ram system and I am running into no problems. Not lagging either, I am having better expierence with ZFS than other FS's. To the OP, I have read somewhere about adding another disk and ZFS will expand and include that disk as well, but you would need to look into that. I am no ZFS expert by no means. I just enjoy using it.
    Also I have read that ZFS doesn't support seperate partitions for swap, I use a ZFS created swap volume.
    Last edited by ndowens04 (2013-09-07 02:16:23)

  • "Backup is too large for backup volume" error

    When I try to backup my StartUp Drive (931.2 GB capacity, 348.2 GB Available, 583.0 GB Used) to my Backup Drive (931.2 Available) which is mounted in the adjacent bay I have begun to get an Error Message that says "This backup is too large for the backup volume. The backup requires 1379.1 GB but only 931.0 GB are available." Clearly something is amiss. It was backing up to this hard drive just fine.
    Here is the log from the Backup Buddy Widget
    Starting standard backup
    Backing up to: /Volumes/2 Backup/Backups.backupdb
    Event store UUIDs don't match for volume: 4 Movies
    Event store UUIDs don't match for volume: 1 Start Up
    Event store UUIDs don't match for volume: 3 Media
    Backup content size: 466.2 GB excluded items size: 0 bytes for volume 4 Movies
    Backup content size: 583.0 GB excluded items size: 1.9 MB for volume 1 Start Up
    Backup content size: 99.9 GB excluded items size: 0 bytes for volume 3 Media
    Starting pre-backup thinning: 1.35 TB requested (including padding), 930.96 GB available
    No expired backups exist - deleting oldest backups to make room
    Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    Backup Failed: unable to free 1.35 TB needed space
    Backup failed with error: Not enough available disk space on the target volume.
    Message was edited by: James Pittman1

    James Pittman1 wrote:
    I installed a new hard drive ( replaced a 250 GB with a 1 T drive), I deleted a sparse image from another drive (neither of these drives were included with the backup from TM) and I renamed the TM drive from "Backup" to "2 Backup" after I erased it. I then attempted the full back up from the "Startup" drive to the newly erased "2 Backup" drive and got the error message. All drives are internal.
    According to the messages you posted earlier, you're trying to back-up three drives:
    Backup content size: 466.2 GB excluded items size: 0 bytes for volume 4 Movies
    Backup content size: 583.0 GB excluded items size: 1.9 MB for volume 1 Start Up
    Backup content size: 99.9 GB excluded items size: 0 bytes for volume 3 Media
    That's a total of 1149.1 GB. TM then adds about 20% for workspace it will need (the "padding" in the next message):
    Starting pre-backup thinning: 1.35 TB requested (including padding), 930.96 GB available
    You need a bigger TM drive, or to back-up one or more of the other drives some other way, and exclude them from TM.
    A 1 TB drive is just barely large enough to back-up your +Start Up+ drive, as TM really should have 2-3 times the space of the data it's backing-up.

  • HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

    Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

    Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
    Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
    So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
    8/19/13 5:18:40.385 PM Console:  Marker - Aug 19, 2013 5:18:40 PM
    8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
    8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:21:53.000 PM kernel: USBF:          58185.  2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
    8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
    8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
    8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
    8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
    During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
    I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

  • Time Machine: The backup volume could not be found?

    I keep getting the message "The backup volume could not be found" when I try to back up my Macbook Pro using an external Lacie USB harddrive. I have tried reformatting the harddrive, and restartet the computer. The external harddrive works normal in Finder, I am able to write and read it, but Time Machine still get this error message. Can anyone help me here?
    When I look in the console log, it sais: Volume at path /Volumes/MBP Backup does not appear to be the correct backup volume for this computer. (Cookies do not match)
    Where can I delete this cookies?

    There is a Time Machine preferences file at
    <your startup drive root>/Library/Preferences/com.apple.TimeMachine.plist
    Note: This is be main Library folder, not the one in your user folder.
    You might try moving that to the Desktop so that the system creates a new one.

Maybe you are looking for