Skip to main content
Participating Frequently
December 12, 2017
Question

Lightroom Classic: Strange "VM" Volume in import dialog box

  • December 12, 2017
  • 12 replies
  • 351 views
Just upgraded to the latest Lightroom Classic CC (7.1 Release).

Noticed following in import dialog box:
Both in the (lefthand) Source column as in the (righthand) Destination column, one of the listed Volumes is "VM" (refer to attached screen shot).

This "VM" Volume is not listed in any Finder window, so I ran DiskUtil to find out what it was. The "VM" Volume appears to be a low level volume on the internal SSD, just like the "Preboot" and "Recovery" volumes (only those two are correctly not listed in the LR Classic CC import dialog box).

My impression is that it's a bug, and that this "VM" volume should be suppressed in the dialog box (shouldn't even be present at this level of the OS).
Any ideas?

Apple MBP (2017 | 15" Retina | 2.9 GHZ Intel i7 | 16GB | 512GB SSD | MacOS High Sierra 10.13.2)


This topic has been closed for replies.

12 replies

Participating Frequently
March 12, 2018
Why has no one from Lightroom/Adobe solidly answered this question about the VM? I have had the same thing showing up and it's annoying - simply because we don't know what it is and why it's there. An answer from adobe staff about what this is and what they are doing about it would be most helpful.
Inspiring
December 25, 2017
I am having the same problems.  Both VM and SS@snap plus 5-digit numbers.  Using Classic now, but don't know when this started.  I use Time Machine to back up my iMac and thought that might be the problem.  
Participating Frequently
December 22, 2017
I am having the same issue with the sudden appearance of a VM folder after upgrading.  Curious to know what this is and how to get rid of it.
Participant
December 19, 2017
Yes, but could someone reply as to what is happening with the Macintosh HD@snap postings I am getting in my Import dialog panel?
Participating Frequently
December 19, 2017
@796284 Zell -- Yes this issue is not specific to particular Lr version.
Participant
December 19, 2017
I can say for certain that it is not a problem of LR CLassic as I have not yet installed it and am having a similar problem as described here:

Two days ago, when I tried to import to LR from my memory card, the left hand panel (sources) included a folder called VM plus several files entitled "Macintosh HD@snap plus five digit numbers". Each of them each of them seems to include everything on my SSD. They do not appear when I search my Finder, but do show up if in LR I right click Show In Finder.I never saw this before and I'd appreciate your advice as to what it is and how to get rid of them. I should add, that these @1387675 entries play hide and seek. Sometimes when I restart LR, some of these entries are present and sometimes none of them is present. Finally, I should note that I have not yet installed LR Classic  butt use version 2015.12 and  I am using a Imac with the High Sierra System.

Many thanks,
Steve Zell

Image is not available

Participating Frequently
December 19, 2017
@Reetesh Mukul: Thank you!
Participating Frequently
December 19, 2017
@WorldShooter -- understand your concern, sure we will look deeper into this issue.
Participating Frequently
December 19, 2017
@Reetesh Mukul:
Appreciate your clarification.
As you can see in the screen shot I provided, Terminal DiskUtil reports the "VM" point as a partition (disk1s4), just like "Preboot" (disk1s2) and "Recovery" (disk1s3). None of those three points are mounted upon system boot. They are not available to the MacOS Finder, not even as hidden disks (trust me, I checked).
So my question remains, why does LR show the "VM" point?
LR doesn't show the "Preboot" or "Recovery" points either, so why should it show "VM"? As far as I understand these are at the same hierarchy level.
Also, LR has never shown anything like this in the past, so why does it start doing that now with the upgrade to LR Classic CC (v7 and beyond).
I appreciate the thoroughness, but I don't understand why this is such a hard issue to determine the correct behavior.

Participating Frequently
December 18, 2017
@WorldShooter -- This means it is hard to determine in which cases we should show VM point and which cases we should not. Till we do not have clear answer on it, it is better to keep it shown. We will think through and experiment with this behavior.