Is it safe to delete LUN/physical disk

Hi all,
I recently had a FC storage system, that had been attached to my former OVM 2 cluster. to my OVM 3 cluster. This storage system provided a RAID5 LUN of 5 TB. When I changed the zone on my FC network, the LUN became visible in OVM3.
Now, I wanted to change the LUN from a RAID5 to a 4x RAID1 LUN, providing less capacity, but more IOPs. So I deleted the LUN and created a new one.
OVMM now shows the old 5 TB LUN and the new 3 TB LUN and I cannot seem to get rid of the "old" LUN. I do have already restarted all my VM servers and none of them does show the 5 TB LUN, so why does OVMM still shows this LUN.
I also tried to rescan the physical disk in the hardware section, but the LUN sticks…, but I am a bit reluctant to delete the nonexistent LUN.
Any advice, anyone?
Thanks

budachst wrote:
but I am a bit reluctant to delete the nonexistent LUN.Delete it. Oracle VM doesn't know that the LUN was purposefully deleted and is waiting for it to come back. It'll probably go into an Error state at some point as well. Keep in mind that the "Unmanaged" part of the Storage Array means that Oracle VM is not doing any pro-active management of that storage. You have to do that manually.

Similar Messages

  • 25K+ Files which uses 30.5GB disk space - Is it safe to delete?

    I am running Oracle 10g on Windows Server 2003 and noticed that the folder D:\oracle\product\10.2.0\db_1\WIN2KSVR_DB1\sysman\recv\errors have 25K+ files which have 30.5GB folder size. Is it safe to delete these files?

    Please refer below MOS doc
    *DB Control directory ../sysman/recv/errors is filled up with xml files. [ID 732725.1]*

  • Duplicate Folders Occupying Physical Disk Space in /Volume

    It all started when I tried to restore from the Time Machine and it threw a error back stating that there is no disk available. I was wondering how come as I have a 120GB Partition for the Mac OS and I only have around 50 GB of data in my folders. I tried to find out what is happening and finally figured that my entire Macintosh HD has a duplicate copy inside the /Volumes folder. I went to the XTERM to investigate and found that the / (root) has a Users folder where all my stuffs like pictures, music, movies, documents reside and the same data or content is duplicated in the /Volumes/Macintosh HD/Users folder
    I first thought that it was only a link, but later was shocked to find out that it is not a link and it is indeed a physical copy of all my User folders inside the /Volumes/Macintosh HD/Users folder and actually occupying almost another 50 GB of my Hard disk space.
    I am not sure how this happened or how it is duplicating itself. I am also afraid to delete the stuffs inside the /Volumes folder as it might crash my system (it is already hidden - I assume it is hidden for some purpose). Please suggest any options, how I can get rid of these duplicated data and how to avoid such duplication in the future and is it safe to delete those duplicated files and folders in the /Volumes path.
    Thanks
    Regards
    Chelvam.S.T

    Those folders may be created if an attempt is made to access another drive when it isn't available to the computer. They can be deleted normally.
    (47014)

  • Assigning folders and files to different physical disks OS X 10.9

    My mid 2010 iMac 27 i7 quadcore, 32 GB memory has two 1 TB SSDs and several 2 to 3 TB 7200 / 5200 SATA, Firewire, LAN and USB external HDs. I would like to direct OS X 10.9 to use frequently accessed System data/images (boot, OS X, utilities and and their attendant folders and files) from SSD 1 and frequently used / accessed applications and their attendant folders and files on the second SSD 2. (I use Microsft Office Word and Excel frequently and also Windows 7 running on VMWare.) Then I would like to keep less frequently used applications and their attendant folders and files on the SATA 7200 external disk (USB 3.0 to 2.0), photos on a fourth external disk (firewire 800), music on a NAS (Raid 1, 1000Gb Ethernet), and movies on a fifth external HD (firewire 800). What I need to know is how to "assign" these various files to a physical disk. Please, I am not looking for opinions and/or guesses. I am looking for a strategy known to work and/or utilites known do set this up easily and correctly. Thanks in advance. BTW, I am a retired OS programmer and software/HW knowlegable. I have no Unix (or of course Apple OS X) programming experience, but have written and modified many other OSs. So one can be reasonably technical with me in their answers. Thanks again, Skip.

    Hope this helps.
    1. Empty Trash.
        http://support.apple.com/kb/PH10677
    2. Start up in Safe Mode
        http://support.apple.com/kb/PH11212
    3. Delete "Recovered Messages", if any.
        Hold the option key down and click "Go" menu in the Finder menu bar.
        Select "Library" from the dropdown.
        Library > Mail > V2 > Mailboxes
        Delete "Recovered Messages", if any.
        Empty Trash. Restart.
    4. Repair Disk
        Steps 1 through 7
        http://support.apple.com/kb/PH5836
    5. Disk space / Time Machine ?/ Local Snapshots
       http://support.apple.com/kb/ht4878
    6. Re-index Macintosh HD
       System Preferences > Spotlight > Privacy
       http://support.apple.com/kb/ht2409

  • Safe to delete Lightroom from my internal hard drive?

    Hi
    I shoot in raw and have been using Lightroom for approx 4 years, most recently Lightroom 4 and before that Lightroom 2. Lightroom is taking up a lot of disk space on my internal hard drive and my computer is not happy.
    I have deleted all but a couple of backups and then copied all my Lightroom lrcat files to an external hard drive. Now, Lightroom will only open if I have that external hard drive plugged in. Great! That is what I wanted. Is now safe to delete my Lightroom files from my internal hard drive? I am not that computer savvy and I am also terrified of losing all my work.
    Thanks

    Well, if you have them on a single external drive and you delete them from your internal drive, then you have only one copy left, correct? In that case you are at extreme risk of losing your one and only copy.
    I worked in the disk drive industry for 30 years and have my lrcat files backed up on three hard drives and two USB sticks. Maybe I'm just paranoid but it's likely a hard drive will eventually fail. And based on experience, for some Murphy's law reason they fail most often for people who have not backed up their data.
    I'll bet there is all kinds of other stuff that can be removed from your hard drive, various temporary files, log files, etc. Try a free app like CCleaner (on Windows) to see what it does.
    But I would not have just one copy of my latest lrcat files in existence.

  • Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server

    I have a physical disk that I can see from multipath -ll  that shows up as such
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
    I have about 50 physical LUNs that my Oracle VM server can see.  I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
    This disk has 3 usable partitions on it, plus a Swap.
    I want to mount the 3rd partition temporarily on the OVM server itself and I receive
    # mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
    mount: you must specify the filesystem type
    If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works.  (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
    Is this possible?

    Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
    I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
    # fdisk -l
    Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/xvdh1   *           1          13      104391   83  Linux
    /dev/xvdh2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/xvdh3            2103       27783   206282632+  83  Linux
    /dev/xvdh4           27784       30394    20972857+   5  Extended
    /dev/xvdh5           27784       30394    20972826   83  Linux
    # mount /dev/xvdh3 /mnt  <-- no error
    # df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/xvda3            197G  112G   75G  60% /
    /dev/xvda5             20G 1011M   18G   6% /var
    /dev/xvda1             99M   32M   63M  34% /boot
    tmpfs                 2.0G     0  2.0G   0% /dev/shm
    /dev/xvdh3            191G   58G  124G  32% /mnt  <-- mounted just fine
    Its ext3 partition
    # df -T
    /dev/xvdh3
    ext3   199822096  60465024 129042944  32% /mnt
    Now if I go to my vm.cfg file, I can see the disk that is presented.
    My disk line contains
    disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
    Multipath shows that disk and says "dm-115" but that does not translate on fdisk
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
    # fdisk -l
    Disk /dev/sdp: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdp1   *           1          13      104391   83  Linux
    /dev/sdp2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdp3            2103       27783   206282632+  83  Linux
    /dev/sdp4           27784       30394    20972857+   5  Extended
    /dev/sdp5           27784       30394    20972826   83  Linux
    Disk /dev/sdab: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdab1   *           1          13      104391   83  Linux
    /dev/sdab2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdab3            1319       27783   212580112+  83  Linux
    /dev/sdab4           27784       30394    20972857+   5  Extended
    /dev/sdab5           27784       30394    20972826   83  Linux
    Disk /dev/sdac: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdac1   *           1          13      104391   83  Linux
    /dev/sdac2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdac3            2103       27783   206282632+  83  Linux
    /dev/sdac4           27784       30394    20972857+   5  Extended
    /dev/sdac5           27784       30394    20972826   83  Linux
    Disk /dev/sdad: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdad1   *           1          13      104391   83  Linux
    /dev/sdad2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdad3            1319       27783   212580112+  83  Linux
    /dev/sdad4           27784       30394    20972857+   5  Extended
    /dev/sdad5           27784       30394    20972826   83  Linux
    Disk /dev/sdae: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdae1   *           1          13      104391   83  Linux
    /dev/sdae2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdae3            2103       27783   206282632+  83  Linux
    /dev/sdae4           27784       30394    20972857+   5  Extended
    /dev/sdae5           27784       30394    20972826   83  Linux
    Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdaf1   *           1          13      104391   83  Linux
    /dev/sdaf2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdaf3            2103       27783   206282632+  83  Linux
    /dev/sdaf4           27784       30394    20972857+   5  Extended
    /dev/sdaf5           27784       30394    20972826   83  Linux
    Disk /dev/sdag: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdag1   *           1          13      104391   83  Linux
    /dev/sdag2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdag3            2103       27783   206282632+  83  Linux
    /dev/sdag4           27784       30394    20972857+   5  Extended
    /dev/sdag5           27784       30394    20972826   83  Linux
    Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-13p1   *           1          13      104391   83  Linux
    /dev/dm-13p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-13p3            2103       27783   206282632+  83  Linux
    /dev/dm-13p4           27784       30394    20972857+   5  Extended
    /dev/dm-13p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-25p1   *           1          13      104391   83  Linux
    /dev/dm-25p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-25p3            1319       27783   212580112+  83  Linux
    /dev/dm-25p4           27784       30394    20972857+   5  Extended
    /dev/dm-25p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-26p1   *           1          13      104391   83  Linux
    /dev/dm-26p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-26p3            2103       27783   206282632+  83  Linux
    /dev/dm-26p4           27784       30394    20972857+   5  Extended
    /dev/dm-26p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-27p1   *           1          13      104391   83  Linux
    /dev/dm-27p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-27p3            1319       27783   212580112+  83  Linux
    /dev/dm-27p4           27784       30394    20972857+   5  Extended
    /dev/dm-27p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-28p1   *           1          13      104391   83  Linux
    /dev/dm-28p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-28p3            2103       27783   206282632+  83  Linux
    /dev/dm-28p4           27784       30394    20972857+   5  Extended
    /dev/dm-28p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-29p1   *           1          13      104391   83  Linux
    /dev/dm-29p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-29p3            2103       27783   206282632+  83  Linux
    /dev/dm-29p4           27784       30394    20972857+   5  Extended
    /dev/dm-29p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-30p1   *           1          13      104391   83  Linux
    /dev/dm-30p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-30p3            2103       27783   206282632+  83  Linux
    /dev/dm-30p4           27784       30394    20972857+   5  Extended
    /dev/dm-30p5           27784       30394    20972826   83  Linux
    How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
    If I try the same command as before with the -t option it gives me this error.
    # mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
    mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
    I know I am close here, and feel it should be possible, I am just missing something.
    Thanks for any help

  • Is it safe to delete iTunes media that is no longer available in the iTunes Store?

    There is a support document that states it is OK to delete content locally so long as the content is available in the cloud depending on your geographic location.  As I'm in the US all media types are available.  From the document:
    You can delete items that you bought from the iTunes Store, App Store, iBooks Store, or Mac App Store from your iOS device, Mac, or PC. Because Apple TV (2nd and 3rd generation) plays content from the cloud, you don't need to delete items from your Apple TV.
    Before you delete an item, make sure you can download it again. If you can't or need to pay to download it again, back up the item before you delete it.
    What I am still not clear on is if it is also safe to delete content that is no longer available in the iTunes store?  Will it still be available for previous purchases?
    I prefer the quality and off-line availability of iTunes media over Google Play but I've had issues recovering deleted media in iTunes in the past and so have less anxiety about the security of my purchases on Google Play versus iTunes.  Can someone confirm if items no longer available for sale in iTunes are or are not still available via the cloud?

    Thanks for the reply although I'm not too happy to hear it.  What's awesome about the cloud is no longer having to keep up with any physical media.  The promise of that is realized with everything else (my work, music, books) besides movies and TV.
    I wonder how Google Play will handle movies/tv that becomes unavailable?  Google Play does allow you to download media in some circumstances (on Android and iOS) but is generally intended  for streaming.  Maybe relying on a physical copy as I do with iTunes should make me more comfortable with it and not less. 
    I will come back to mark your reply as the solution as it becomes clear there is not a contrary position.  Thank you.

  • Physical disk for OS and read only filesystem after live migration

    I am running OVM 3.1.1 connected to an EMC storage array.  I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository.  When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem.  Is this an unsupported configuration or do I have potential problems with my LUN mapping?  Has anyone seen this problem before?

    I am running OVM 3.1.1 connected to an EMC storage array.  I have a situation where physical disks are being used for OS and binary filesystems (i.e. /u01, etc..) rather than virtual disks inside a repository.  When a VM is migrated from one host to another, I sometimes get a message stating the size of the disk changed and shortly afterwards the filesystem is changed to read only and I have to reboot to fix the problem.  Is this an unsupported configuration or do I have potential problems with my LUN mapping?  Has anyone seen this problem before?

  • Is it safe to delete CiFiles folder on Windows storage Server 2008

    Hi Team,
    .ci file growing in "C:\Documents and Settings\All Users\Application Data\Microsoft\Search\Data\Applications\Windows\Projects\SystemIndex\Indexer\CiFiles" location. Is it safe to delete the CI file. please let me know, any other way to disable
    the growth of CI files.
    What is the route cause? This is file server using windows storage server 2008 OS.
    How to avoid in future this type of issue?
    My total hard disk size 80 GB but now free space only 110 Almost full my hard disk. So please help to advise how to clear
    all ci files?
    Thanks in advance 

    Hi,
    When you use indexing service, the service create .ci files. The files are content index files on the server. As long as the service is not running you should not encounter any problems if you delete the folder.
    Is it safe to delete CiFiles folder on Windows Server 2008 R2
    http://www.wincert.net/tips/windows-server/1948-is-it-safe-to-delete-cifiles-folder-on-windows-server-2008-r2
    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
    Regards,
    Mandy
    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.

  • How can I delete the update installation files? Or which files are useless and safe to delete?

    ThinkVantage System Update application will find the appropriate updates, download them and install them. This is convenient. But when it finishes the updates, it will not clean the installation files it has downloaded, which I think are not useful any more since the update installation is completed, right?
    I think the update appliction stores the downloaded files in the folder: C:\Program Files\Lenovo\System Update\ ,   this folder of mine is over 1.32GB big now. But I just don't know which files and subfolders in it are safe to delete.
    Or rather, the preload system occupies a large space on the disk. Which files are no longer used and safe to delete?
    Would any experts help with this? Thank you very much!
    Norm

    I've been experimenting. Now I figure it out. Automatic System Update downloads and stores files in C:\Program Files\Lenovo\System Update\ Sessions\, and in Sessions' subfolders, all files are not used once update is completed except those ending with .xml. Thus those unnacessary files are safe to delete.
    This is what I find out so far.
    Continuing to experiment.
    Message Edited by normyy on 05-31-2009 11:12 PM

  • In iPhoto '11, is it safe to delete aliases in the masters folder?

    I'm running the latest update of iPhoto '11.
    I'm trying to do some house cleaning and I'm discovering many duplicates of photos because I used to have iphoto copy pictures into the library.
    So, I'm getting rid of duplicates, and I keep coming across these folders which have aliases to the original picture (not in the library).
    I've noticed that some of these aliases are pointing to pictures that are no longer there (i.e. I deleted them a long time ago).  So I was wondering if it's safe to delete the aliases.
    I've noticed that any photos added in '11 dont actually have aliases.  Only the photos added in prior versions.
    On a similar note, if it's not safe to delete the aliases, then if I did delete them, would they be recreated somehow? (like, if i rebuild the library database by pressing "command" and "option" on iphoto launch....or something).
    Just curious so I can continue my house cleaning.
    Thanks in advance.

    It's impossible to say whether it's safe to delete those aliases or not. What you're doing is simply not supported.
    There are two possible uses for aliases in an 11 Library. One is linking up the old Library to the new structure. The other is to track referenced files. So, good luck with that.
    I'm sure you've thought this decision through but for the benefit of others who may be thinking of this:
    A Referenced Library is when iPhoto is NOT copying the files into the iPhoto Library when importing. The files are then stored where ever you put them and not in the Library package. In this scenario you are responsible for the File Management.
    This is an attractive option for some users at face value, but it contains a significant number of issues that you might want to consider before making the decision to run a Referenced Library
    How to do it:
    iPhoto -> Preferences -> Advanced and uncheck the box at 'Copy items to the iPhoto Library'
    Now when you import iPhoto makes an alias in the Library Package that points to the stored file. Note: iPhoto still creates a thumbnail of the image and it makes a Preview of edited photos inside the Library Package.
    Issues?
    1. You are responsible for file management. That's more work:
    You must first move the files from your camera to the storage location before importing.
    If you want to delete files then you must first trash them from iPhoto and then afterwards find them in your storage and trash them.
    Thereafter, you cannot move the files on early versions of iPhoto at all, on iPhoto 08 and later you may move them on the same Volume or Disk. If you move them to a new volume or disk the aliases my break. If they are on an different volume and you move them the aliases will break.
    You cannot rename the files.
    Migrating: moving to a new machine, moving the files to another disk are all a lot more complex.
    2. You gain no extra functionality from running a Referenced Library. Nothing. This is just storage. You still manage the files via iPhoto. You edit them with iPhoto or via iPhoto's External Editor setting, otherwise you're changes will not be available in iPhoto. You don't save  byte of storage space.
    3.  If you have the Library on one volume and the photos on another you if anything changes in the path to a file (Like if you upgrade your machine, move the files on the NAS or on to another one?) then the alias will break, and you'll have to repair it manually. For every photo in the Library. One at a time.
    Why do you want to run a Referenced Library?
    Because my photos won't fit on my HD?
    You can run a Managed library from an external disk. Make sure the drive is formatted Mac OS Extended (Journaled)
    1. Quit iPhoto
    2. Copy the iPhoto Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
    4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
    You're worried about accessing the files?
    There are many, many ways to access your files in iPhoto:   You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Command-Click for selecting multiple pics.
    (Note the above illustration is not a Finder Window. It's the dialogue you get when you go File -> Open)
    You can access the Library from the New Message Window in Mail:
    There's a similar option in Outlook and many, many other apps.  If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
    If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
    If you want to access the files with iPhoto not running:
    For users of 10.6 and later:  You can download a free Services component from MacOSXAutomation  which will give you access to the iPhoto Library from your Services Menu.
    Using the Services Preference Pane you can even create a keyboard shortcut for it.
    For Users of 10.4 and 10.5 Create a Media Browser using Automator (takes about 10 seconds) or use this free utility Karelia iMedia Browser
    Other options include:
    Drag and Drop: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
    File -> Export: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
    Show File:  a. On iPhoto 09 and earlier:  Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.    3.b.
    b: On iPhoto 11 and later: Select one of the affected photos in the iPhoto Window and go File -> Reveal in Finder -> Original. A Finder window will pop open with the file already selected.
    Regards
    TD

  • What is taking up all the room on my 160GB HD? And what is safe to delete?

    I am new to Mac, and have a Macbook Pro, OSX 10.5.8, with a HD of 160GB. I use an external HD to back up my Home Folder and for Time Machine (which may be redundant, not sure). I use iDisk to back up my Personal Data and Settings.
    There is a HUUUUGE (76GB!) file of backups on my Mac HD, which is probably the backup Home files from Time Machine before I began using an external HD for backups.
    Questions:
    What files on the Mac HD are safe to delete, and what is the best way to do so? (Backup files, logs, anything else to free up HD space?)
    If I'm using an Ext HD (500GB) for Time Machine, do I ALSO need to back up my Home Folder there, too?
    And should I use a completely separate ext HD to back up my OSX? I have not yet backed this up.
    Random question: what is a .dmg file, and
    Thanks for any help. I may be over-doing the backups, but coming from a PC world, where pressing one button makes things go "poof", I don't mind some redundancy.

    Keysfins,
    First let's remember that 160GB is not a very large HD by today's standards. If you are intending to use your MBP for items that take up a lot of HD space such as photos, video or music then I think it would be wise to either upgrade the drive to a larger drive or to store that information on a second external HD. I would not recommend deleting any of the files on your internal HD with the exception of data files you may have already created.
    When you use TM the first time it will back up 100% of the internal drive, after that it backs up just files that have been added or changed so you Home Folder is backed up automatically and yes they should be.
    You can also get another external HD for creating a bootable clone, these are useful if the internal drive has a fatal crash. With a bootable clone this gives the peace of mind that if you do have a fatal crash you can be up and running in minutes. In order to create a bootable clone you would need either SuperDuper or Carbon Copy Cloner. Both apps do the same thing however SuperDuper is $28 and offers support for that price where CCC is free with no support. The difference between a cloned drive and TM is that TM creates hourly backups and is not a bootable drive whereas a cloned drive is a snapshot in time (you choose when) of the internal drive and is bootable. Many people (including myself) use both TM and a bootable clone, it just depends on your level of paranoia regarding backups. There is an excellent article in MacWorld that talks about back up strategies based on your degree of worry. The link for that article is here.
    Last a .dmg file is a disk image file, in short when you get a new application (like CCC, SuperDuper etc...) you will probably receive them as a .dmg file. Here is an article that gives you a little more information if you are interested.
    Regards,
    Roger

  • How to map ASM disk path to physical disk on AIX?

    Hi Everyone,
    I am working on a plug-in for Oracle Enterprise Manager 10gR2 on AIX 5.3 which provides monitoring of storage arrays and supports ASM databases in addition to the 'emrep' database. One of the metric of that plug-in is populated by the result from a korn shell script. The script directly runs on the AIX host (connected to the storage array by FC cables via HBA ports) and retrieves the mapping for -- Physical disk - Logical Disk - LUN - ASM Disk.
    Now, I was able to get the mapping for Physical Disk – Logical Disk – LUN, but could not map ASM Disk. I googled a lot for any clue but did not find the answer to this specific problem.
    Now, I have the list of physical disks used for ASM by the command—
    lspv
    hdisk0 0001c22ac8d664ca rootvg active
    hdisk1 0001c22aa51f496a Oracle active
    hdisk2 0001c22ac478263a scratch active
    hdisk3 0001c22ac472549a Oracle active
    hdisk4 0001c22ac4725d6a Oracle active
    hdisk5 none None
    hdisk6 none None
    hdisk7 none None
    hdisk8 none None
    hdisk9 none None
    hdisk10 none None
    hdisk11 none None
    hdisk12 none None
    hdisk13 none None
    hdisk14 none None
    hdisk15 none None
    hdisk16 none None
    The disks hdisk5-16 are ASM disks and there are no PVID’s present.
    I also have the list of ASM disks by the command—
    ls –l /dev | grep oracle
    crw-rw---- 1 oracle dba 22, 6 May 12 00:02 asm_rd10_1a
    crw-rw---- 1 oracle dba 22, 10 Apr 21 07:27 asm_rd10_1b
    crw-rw---- 1 oracle dba 22, 7 May 09 13:53 asm_rd10_1c
    crw-rw---- 1 oracle dba 22, 8 May 09 13:53 asm_rd5_1a
    crw-rw---- 1 oracle dba 22, 4 May 12 00:02 asm_rd5_1b
    crw-rw---- 1 oracle dba 22, 9 Apr 21 07:28 asm_rd5_1c
    crw-rw---- 1 oracle dba 22, 12 May 12 00:02 asm_xbb2_rd10_1a
    crw-rw---- 1 oracle dba 22, 11 Apr 24 07:34 asm_xbb2_rd10_1b
    crw-rw---- 1 oracle dba 22, 13 May 09 13:53 asm_xbb2_rd10_1c
    crw-rw---- 1 oracle dba 22, 16 May 12 00:02 asm_xbb2_rd5_1a
    crw-rw---- 1 oracle dba 22, 14 Apr 24 07:34 asm_xbb2_rd5_1b
    crw-rw---- 1 oracle dba 22, 15 May 09 13:54 asm_xbb2_rd5_1c
    Now I am looking for a way to map these two lists with each other, and had no luck so far.
    Does oracle provide this information somewhere in the OEM installation structure or is there a command in AIX which could give some way to map the ASM disks to the physical disks?
    Any help on this is greatly appreciated. Thanks in advance…
    FYI: ASMLib driver is not present on the system.

    The view you are talking about here gives the ASM DISK NAME (like DGRXBB_0001) and ASM DISK PATH (like /dev/asm_rd_10_1a) and I am already using it, but this is not what I asked in mt original post. If you read carefully, I want to establish a mapping between the ASM DISK PATH (like /dev/asm_rd_10_1a) and the AIX Physical disk (like /dev/hdisk5) and did not find any view giving this info. If you know of some views which could help establish this mapping or some AIX commands or files that could help do this using shell script, it is most welcome

  • When I activate icloud on my iphone, is it safe to delete previously made computer back-up files ?

    When I activate icloud on my iphone, is it safe to delete previously made computer back-up files ?

    It is used for syncing/pushing data to your other devices, and for backing up. It does not add to the physical capacity of your device.

  • Powershell- Associate Mount Point to Physical Disk

    I need to be able to associate mount points (Get-WmiObject -Class Win32_MountPoint) with the physical drive on which it resides.
    Scenario: I have physical disks (SAN LUNs) mounted as folders on an E: drive (also a SAN LUN) of a server.  I need to be able to, via a PowerShell script, associate the "folder" name to the physical disk (i.e., Harddisk4 or PhysicalDrive4).
    I can get Mount Point associated with the Volume, etc., but can't make the link to the physical disk.
    Any help is appreciated.

    Unfortunately there isn't an association class between mount points and physical disks like there is between logical and physical disks. I did a blog about finding partition alignment which required using Win32_LogicalDiskToPartition class. One of the comments
    suggested using Sysinternals diskext as workaround. See comments:
    http://sev17.com/2009/02/disk-alignment-partitioning-the-good-the-bad-the-ok-and-the-not-so-ugly/

Maybe you are looking for