Unique IDs- Case sensitive

In my directory, for user UID is my DN(Distinguished Name). So no one should be able to have the same UID. Yet, if you change the case, the directory still allows it. I cannot find the attribute in the config that prevents this. Any suggestions?

First, I think you'll need to use DSEE 7, as previous versions don't enforce any syntax checking. That is, previous version won't complain when you import some data that doesn't comply with the schema. You'll be able to have strings values for integer attributes with those versions.
Then, you need to use a case sensitive attribute as RDN. Since uid is not case sensitive, DSEE 7 treats uid values without distinction between lower and upper cases.
Another option that I would not recommend would be to change your schema and modify the standard uid attribute definition to make it case sensitive. Rather consider creating a brand new attribute of your own .

Similar Messages

Unique IDs

Does anyone have a good method for creating integer IDs that are
guaranteed to be unique for a given partition, regardless of how many
tasks are running on the partition, without a network hit, and will work
on both client and server partitions?
Any ideas would be appreciated.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Chris Johnson
BORN Information Services Group
Forte National Practice
http://www.born.com
Mailto:[email protected]
612-404-4409
612-404-4440 (fax)

First, I think you'll need to use DSEE 7, as previous versions don't enforce any syntax checking. That is, previous version won't complain when you import some data that doesn't comply with the schema. You'll be able to have strings values for integer attributes with those versions.
Then, you need to use a case sensitive attribute as RDN. Since uid is not case sensitive, DSEE 7 treats uid values without distinction between lower and upper cases.
Another option that I would not recommend would be to change your schema and modify the standard uid attribute definition to make it case sensitive. Rather consider creating a brand new attribute of your own .

Mac OS X, User Folder and Case-sensitivity (plus a Partitioning Question)

Hello everybody.
Today, I'd like to start a new thread regarding the configuration of OS X and the formatting of the drive with a HFS+ (case-sensitive, journaled) file system.
There is a problem that has been tormenting me for quite some time now, and so far I haven't been able to find a losution yet.
Here is the issue. When I bought my MacBook Pro (early 2011), I changed the main dirve to an hybrid SSD destinating the original 750GB to a Time Machine backup disk. As a consequence I had to make a fresh install of OS X. When it came the time of formatting I've opted for:
Creating two partitions: 1 for the OS and 1 for the user folder (I have only one admin-user). Back then, I was coming from a Win enviroment and having two partitions seemed to be the best option for me. (Less chanche of user-data corruption in case something goes wrong in the OS partition).
Chose a HFS+ (case-sensitive, journaled) file system. It seemed to be the more complete alternative.
Everything was absolutely for a couple of months then I encountered the first issue: Adobe products don't work on a case-sensitive fs.
I managed to get Photoshop to work eventually (manually correcing folders name) and didn't care too much about the rest.
In the meantime over a year has passed and I kept the mentioned configuration, uptdating to Lion and ML. Recently another couple of isses have appeared: AutoCAD presents the same problem as Adobe and there is an issue in the keyboard balcklight control (from forums seems that ML is not able to store any information in System Preferences regarding the backlight).
Despite the fact that case-sensitive fs seems to be the future solution chosen by Apple, it is still premature to have it as OS fs unless you are an hard-core developer that don't care about tons of programs that would eventually miss from your application folder.
Being decided to move back to a case-insesntive fs, I need wish I could calrify a couple of doubts before proceding:
(Not relatete to fs) Is it a good practice to keep user folder on a separate volume? Does it generates any issue on the base of your experience?
Is it possible to have the OS on case-insensitive fs and the user folder on a case-sensitive one? Does the OS have an issue with that?
The second point is the most critical as my data are now on a case-sensitive volume. They mostly consists in documents, images and music which should be migrated on a case-insensitive volume seamlessy, however, I'm not 100% sure about what happened during the last year (i.e. if there has been the generation of not-unique names).
Furhtermore, I wish I could keep a case-sens volume as I plan to be dealing with a Linux enviroment soon. If that could be the user volume, this would be amazing.
I'd also like to ask personal opinion on advantages of having case-sens fs.
I understand I asked lots of questions in a single post. I hope, however, that this thread could be a base to collect some of the quite dispersive topics related to case-sensitivity present on the web.
Best Regards,
Alexander

alexanderxc wrote:
Linc, in the provious post you said there might be issues having user data on a separte partition.
Which kind of issues are you tihnking of? Have you ever encountered such problems?
The biggest risk is that poorly written software will assume your home directory is at /Users/you and will fail (or worse) if it doesn't like what it finds there.
I really appreciated if you could be more specific and don't worry about being too technical.
There are two ways you can go about it.
1) Set everything up normally as if you only had one partition. Create your user on that one parition. Then, copy all the real user data to the 2nd partition. Using your admin account, make sure that all the permission on the user folder on the 2nd partition are the same as on the original partition. The, use System Preferences > Users & Groups > your account > right/control click > Advanced > Home directory and change it to the home directory on the 2nd partition. Log in to that new account. Make sure everything works. Then delete the user directory at /Users.
2) A even more robust, old-school option is to create an /etc/fstab file and have your 2nd partition mounted at /Users. Then, everything will function normally and your user home directories will all be at /Users. /Users will, however, be on a different volume.

Can't restore from case sensitive TM back-up

I'm in the final stages of restoring my system following a complete rebuild, and am having an issue stop me from restoring all of the files from my TM backup.
Prior to the rebuild it appears that I had my main drive formatted as Extended (case sensitive). Likewise, my TM backup drive was also formatted as case sensitive.
Since the rebuild my main drive is now not formatted as case sensitive, and while I can restore most of the files from the TM backup, there are a small number that won't restore, giving the error message:
+"You cannot copy 'ABCDE' to the destination because its name is the same as the name of an item on the destination, except for the case of some characters."+
As I'm restoring to what was an erased drive, the files can't already exist somewhere else on the drive. Also, it seems odd that most files aren't affected by this, while some are - both data and applications.
I've tried to restore to another case sensitive drive, change the file name something unique so that I could then copy to the non-case sensitive drive, but in the process of copying, the same message appears and the copy fails.
Is there some way to restore individual files from a case sensitive TM backup to a non-case sensitive drive, or to change whatever is causing this within Terminal (note that I'm a complete Terminal novice)
Thanks in advance.

+"You cannot copy 'ABCDE' to the destination because its name is the same as the name of an item on the destination, except for the case of some characters."+
As I'm restoring to what was an erased drive, the files can't already exist somewhere else on the drive.
The files weren't on the drive before the restore started. The restore created them. If the case-sensitive backup has multiple files of the same name (except for case) in a folder, the first will be restored, then you will get the error message when it tries to copy the second.
Also, it seems odd that most files aren't affected by this, while some are - both data and applications.
Most files have different names.

How to make PowerPivot case sensitive?

Hi all,
I just discovered that PowerPivot is case-insensitive, which is quite a big problem for me. The only discussion of this I found so far is here: http://dennyglee.com/2010/06/18/powerpivot-you-are-so-insensitive-case-that-is/ .
That didn't fully answer my question though, is it possible to change this behaviour and make it case sensitive?
The reason it's a problem for me is that I have a column (from external data source) used as an ID in a relationship, which contains a string of random characters. If it so happens that two entries have an ID which only differs by a case of a letter, everything
blows up. More precisely, I can no longer import the data into the table where the column is used as a PK, because it is not unique.
Thanks for any comments,
Jurgis

You can post bugs on Connect.
Thanks!
Ed Price, SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Cannot insert more than 1 WSUS update source with different unique ids

Hello LnG
I am aware that are a whole bunch of forum threads on this error however little bit of additional help would be of great help, as I have nearly tracked this 'pain' down.
Our environment: SCCM 2007 R3
1 Central
15 Primaries and a whole bunch of secondaries
Single WSUS server
OK, so we have just taken handover of this new account and still getting a hang of the creek and corners in the environment. We have about 1000 machines sitting in "Failed to download updates" state. Error
= 0x80040694
WUAHandler.log:
Its a WSUS Update Source type ({A2762CA9-9739-4260-9C3A-DC4B36122E16}), adding it
Cannot insert more than 1 WSUS update source with different unique ids
Failed to Add Update Source for WUAgent of type (2) and id ({A2762CA9-9739-4260-9C3A-DC4B36122E16}). Error = 0x80040694.
Its a WSUS Update Source type ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}), adding it
Existing WUA Managed server was already set (http://WSUSServername:8530), skipping Group Policy registration.
Added Update Source ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}) of content type: 2
WUAHandler
Async searching of updates using WUAgent started.
Checked the
CI_UpdateSources table and found 2 Update sources unique ids:
{BCB9D60B-2668-459B-BFFD-6DDD11AADC53} Date Created 2011-01-11 03:47:52.000/Date Modified 2011-01-11 03:47:52.000
and
{A2762CA9-9739-4260-9C3A-DC4B36122E16} Date Created 2014-07-09 02:48:46.000 / Date Modified 2014-07-09 02:48:46.000
My questions:
Can I rely on the last modified/created date for inactive update source and delete it off the database? in this case can I delete {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}?
When i browsed to the registry location on the Central Server
HKLM\Software\Wow6432Node\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER i saw the update source as {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}.
Does it imply that a stale record?
Any help/guidance will be much appreciated :)

Well!! My wsyncmgr.log says this:
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX1 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX2 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX3 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX4 to 18
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX5to 1
Set content version of update source {BCB9D60B-2668-459B-BFFD-6DDD11AADC53} for site XX6 to 18
So, this is an active update source! ?? I cannnot uninstall and reinstall SUP currently. Any thoughts?? Any ody?

Question: Do Any Mac/Lightroom users use a case-sensitive filesystem?

I know most people use the default case-insensitive Mac filesystem. But plugins may have issues in a case-sensitive filesystem (if not explicitly programmed to handle case), which I just learned is an option for Mac users. Just wondering if any Lightroom users actually do it.
Thanks,
Rob

areohbee wrote:
I'm starting to think that having a case-sensitive filesystem on Mac would only be done by people with very special purposes in mind - e.g. developers who want to test unix command-line apps..., and would "always" be accompanied by case-insensitive volumes for normal Mac use - e.g. Lightroom-data/plugins/photos...
Ya think?
Almost certainly.
As I mentioned before, case-sensitivity is required for, among other things, POSIX compliance, which is of particular interest to a segment of the enterprise and interoperability spaces. Microsoft achieves this by a kernel change (and one of two POSIX-for-Windows licensed libraries) and offering a case-sensitive file system, NTFS. Apple achieves this by offering a way to make HFS+ case-sensitive, with kernel services and a BSD POSIX subsystem that is case-sensitive to the extent the file system is.
Note that apps that treat filespecs as unique when they differ only in case are not necessarily "poorly coded" as this would depend on context and application. There are some very, very good reasons to do so. In fact, one could make an argument that apps that cannot handle a case-sensitive environment are the poorly coded examples. Blindly assuming the case of a filespec makes it unique, or rewriting an existing filespec to a "corrected" one, are very dangerous assumptions.
For most of us, the defaults are more natural, and I would hazard a guess that Lr gets little or no QA under such environments. I know of at least one corner-case (exposed here) that would probably break.

Installation of Photoshop CS6 (Extended) on Case-Sensitive Drives

I understand that under the "system requirements" the Adobe website says that you can't install PS CS6 (Extended) on case-sensitive drives (I'm using a MacBook Pro, OS X v. 10.7.4). This seems to have been the case at least since CS5.
I didn't see this, and I bought (quite excitedly) the update from CS PS5 (Extended) to PS6. I had NO PROBLEM installing PS5 on this drive.
Of course, as other users have indicated, the installer refuses to let you install on a case-sensitive drive (e.g., no options to install on another disk). There is also no mention that CS6 must be installed on the boot drive.
Requiring installation on the boot drive has serious implications for those of us who require case-sensitive drives for other work; I don't want to have to reboot from another drive when I use PS, and switch back and forth -- that's simply foolish.
From my point of view (as a user, granted), this is lazy programming, and this needs to be fixed ASAP. At least in my case, I have a $400 lump of software just taking up space, when I want to be up to my eyeballs enjoying PS6 in all it's glory.
Outside an Adobe fix, I don't see a solution to this problem. If I wipe my drive, format it as not case-sensitive, then I lose functionality for other critical work. Further, I'm not sure that the process of wiping the drive, formating it as non case-sensitive, and restoring everything from TimeMachine would even work (since the backup material is coming from a case-senstive drive and trying to go to a drive that is not case-sensitive).
The REALLY frustrating part is that I've installed Photoshop 3, 4, and 5 (and from much, much further back) on case-sensitive disks -- all with no problems. It's only now that the issue smacks me in the face.
There's got to be a work-around, if not a "real" solution.
Whatever help you might be able to offer would be greatly appreciated; details can be sent to cdretk at gmail dot com.
I have hope, and I thank you in advance.

Whether it is Apple or Adobe's work flow isn't the issue. Between the two
of them, if they are going to support both naming variants, then at both
Adobe and Apple:
1. You MUST use the same case file names. (E.g. FrameWorks and not
Frameworks) EVERY time. And refer to them in your programs and
configuration files the same way EVERY time.
2. You may NOT in your development code use different but case invariant
file names for different files.
3. Your libraries must do the Right Thing.
What gets me is that few others seem to have this problem. Perhaps Adobe
needs to abandon Apple development software, and roll their own outside the
standard system libaries.
Further searching shows that it is not a problem unique to Adobe. The
games BeJeweled, and BZFlag have this issue, as does the Steam game support
systems.
In every case I've run down to date, it has been a violation of #1.
Now there are workarounds: A script that creates appropriate symlinks on
case sensitive file systems would be fairly easy. It would impose some
minor amount of extra overhead.
I bought a copy of Adobe Creative Suite. I returned it unopened. You lost
a sale. Furthermore, until it is fixed, I will mention this at every
opportuity as an exampled of a combination of sloppy workmanship, and
customer indifference on the part of Adobe.
Tell your bosses, Chris, they need to fix this.
Respectfully,
Sherwood of Sherwood's Forests

How make IN operator not case sensitive ?

create table Payment_Methods (
Payment_Method_ID number primary key,
Payment_Method varchar2(11)
check (Payment_Method in ( 'Cash','Check','Credit Card' ) ));
the problem here .... if I insert in the Payment_Method column
by lower case or by upper case , the error will appear like this :-
SQL> insert into Payment_Methods values (
2 1,'cash');
insert into Payment_Methods values (
ERROR at line 1:
ORA-02290: check constraint (DE.SYS_C0010420) violated
and if upper case :-
SQL> ed
Wrote file afiedt.buf
1 insert into Payment_Methods values (
2* 1,'CASH')
SQL> /
insert into Payment_Methods values (
ERROR at line 1:
ORA-02290: check constraint (DE.SYS_C0010420) violated
only initcap case working (like I wrote in create table statement )
SQL> ed
Wrote file afiedt.buf
1 insert into Payment_Methods values (
2* 1,'Cash')
SQL> /
1 row created.
How can I make the Payment_Method column NOT case sensitive ??!!!!

I don't understand this check constraint at all. What is the purpose?
You have a table to hold all possible payment methods. At the same time you are not allowing any new payment methods but the ones defined in the check constraint.
Either use a check constraint to check the correct spelling without checking the values, like check (InitCap(Payment_Method) = Payment_Method) or use a database trigger and a unique key constraint to transform all new values to the correct spelling method (UPPER or INITCAP).

In ALV Report Filter selection should be case sensitive

Dear All,
since one field is case sensitive in database table , i have to fetch that in alv report , but when i am applying filter on that field its is simply fetching data with case description. if its in caps it should fetch caps data but in smaal case report showing no data
Regards,
Pankaj Vashista

Hi,
All text datas are case sensitive.
To make it work perfectly You have to Use the Keyword translate to Upper Case than display
Now filter can work.
Without Transalation to Upper Case filter will not work.
Regards
Arbind

How do I install PSE8 on MAC with case sensitive drive?

I tried to install PSE8 for mac and i get an error saying it cannot be installed on a case sensitive drive.
Is there a fix for this?

What is the purpose of this?
I have my drive formatted case sensitive on purpose for more security and stability.
Why on earth would y'all choose to do this?

Is a Full Text Index search case sensitive or not in SQL Server 2012?

I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
Hanan

Whats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

I am unable to reinstall Photoshop CS6 (I do have the serial number) on my Macbook Pro 10.9.5 (Mavericks os). and am getting the message "Installation on case-sensitive volumes is not supported. Please choose a different volume for installation." I am f

I am unable to reinstall Photoshop CS6 (I do have the serial number) on my Macbook Pro 10.9.5 (Mavericks os). and am getting the message "Installation on case-sensitive volumes is not supported. Please choose a different volume for installation." I am further told that "Adobe apps cannot be installed on case-sensitive drives, you need to Install the product onto an HFS+ or HFSJ non-case-sensitive drive."
What I don't understand is this: I originally bought and installed Photoshop CS6 back in March 2013, and it worked fine. Yesterday my hard drive had to be replaced and my computer person salvaged as much of what was on it as he could, but now I have to reinstall Photoshop. 1) Why did it work before and it's not working now? 2) Is there anything I can do that does not involve reformatting the hard drive?

It means what it says. The "computer person" formatted it wrongly/ unsuitably. it needs to be formatted again.
Error "Case-sensitive drives not supported" or similar install error | Mac OS
Mylenium

Print dialog options in case sensitive file system

Since changing the file system running Lion and Mountain Lion from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled), certain features in print dialogs have disappeared.
Particularly the option to print notes with slides in Microsoft Powerpoint are gone. Also, when choosing to print only 1 (or more, but not all) of multiple pages in Microsoft Word, the printer will nevertheless print all pages.
This problem occurs on printers of different brands, i.e. HP, Lexmark, Brother.
I was able to determine this problem by reproducing the issue on a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Case-sensitive, Journaled) vs a cleanly installed Macbook Pro with OS X 10.8 formatted as Mac OS Extended (Journaled), not Case-sensitive.
Has anyone else had the same problem and maybe a solution?

I just fixed this on my Mac. It is a bug in Microsoft Office... the Printer Dialog Extension (PDE) for Powerpoint is located in a directory named "Plugins", but PowerPoint is looking for it in "PlugIns". This obviously does not work in a case-sensitive filesystem.
Here are the steps to fix the issue:
http://apple.stackexchange.com/a/119974/69562

How can I backup data from a case-sensitive volume to a NON-case-sensitive volume?

The case-sensitive volume in this instance being a desktop-mounted disk image volume.
A tragi-comedy in too many acts and hours
Dramatis Personae:
Macintosh HD: 27" iMac 3.06GHz Intel Core 2 Duo (iMac10,1), 12 GB RAM, 1 TB SATA internal drive
TB1: 1 TB USB external drive
TB2: 2 TB USB to Serial-ATA bridge external drive
Terabyte: a .dmg disk image and resulting desktop volume of the same name (sorry, I don't know the technical term for a .dmg that's been opened, de-compressed and mounted -- evanescently -- on the desktop)
Drive Genius 3 v3.1 (3100.39.63)/64-bit
Apple Disk Utility Version 11.5.2 (298.4)
Sunday morning (05/08/11), disk utility Drive Genius 3's drive monitoring system, Drive Pulse, reported a single bad block on an external USB2.0 1TB drive, telling me all data would be lost and my head would explode if I didn't fix this immediately. So I figured I'd offload the roughly 300 GB of data from TB1 to TB2 (which was nearly empty), with the intention of reinitializing TB 1 to remap the bad block and then move all its data BACK from TB 2. When I opened TB1's window in the Finder and tried to do a straight "Select All" and drag all items from TB1 to TB2, I got this error message:
"The volume has the wrong case sensitivity for a backup."
The error message didn't tell me WHICH volume had "the wrong case sensitivity for a backup," and believe me, or believe me not, this was the first time I'd ever heard that there WAS such a thing as "case sensitivity" for a drive. I tried dragging and dropping some individual folders -- some of them quite large, in the 40GB range -- from TB1 to TB2 without any problem whatsoever, but the majority of the items were the usual few-hundred-MB stuff that seems to proliferate on drives like empty Dunkin' Donuts coffee cups on the floor of my car, and I didn't relish the idea of spending an afternoon dragging and dropping dribs and drabs of 300GB worth of stuff from one drive to another.
Being essentially a simple-minded soul, I had what I thought was the bright idea that I could get around the problem by making a .dmg disk image file of the whole drive, stashing it on TB2, repairing and re-initializing TB1, and then decompressing the disk image I'd made of TB1, and doing the "drag and drop" of all the files in resulting desktop volume to TB1. So I made the .dmg of TB1, called "Terabyte," stashed that .dmg on TB2 (no error messages this time), re-initialized and then rebooted the iMac from my original Snow Leopard 10.6.1 disks and used Disk Utility to erase and initialize TB1 -- making sure that it was NOT initialized as case-sensitive, and installed a minimal system on TB1 from the same boot. Then I updated that 10.6.1 system to 10.6.7 with System Update, and checked to see that Disk Utility reported all THREE drives -- internal, 1TB, and 2TB -- as Mac OS Extended (Journaled), and no "case sensitive" BS. I also used Drive Genius 3's "information" function for more detailed info on all three drives. Except for the usual differing mount points, connection methods, and S.M.A.R.T. status (only the Macintosh HD internal, SATA 1TB drive supports S.M.A.R.T.), everything seemed to be oojah-***-spiff, all three drives showing the same Partition Map Types: GPT (GUID Partition Table.) Smooth sailing from here on out, I thought.
Bzzzzt! Wrong!
When I opened the Terabyte .dmg and its desktop volume mounted, I tried the old lazy man's "Select All" and drag all items from the desktop-mounted drive "Terabyte" to TB1, I got the error message:
"The volume has the wrong case sensitivity for a backup."
I then spent the next three hours on the phone with AppleCare (kids -- when you buy a Mac ANYTHING, cough up the money for AppleCare. Period.), finally reaching a very pleasant senior tech something-or-other in beautiful, rainy Portland, OR. Together we went through everything I had done, tried a few suggestions she offerred, and, at the end of three hours, BOTH of us were stumped. At least I didn't feel quite as abysmally stupid as I did at the beginning of the process, but that was all the joy I had gotten after two solid days of gnawing at this problem -- and I mean SOLID; I'm retired, and spend probably 12 hours a day, EVERY day, at the keyboard, working on various projects.
The AppleCare senior tech lady and I parted with mutual expressions of esteem, and I sat here, slowly grinding my teeth.
Then I tried something I don't know why I was so obtuse as to not have thought of before: I opened Apple's Disk Utility and checked the desktop-mounted volume Terabyte (Mount Point: /Volumes/Terabyte), the resulting volume from opening and uncompressing the .dmg "Terabyte".
Disk Utility reported: "Format : Mac OS Extended (Case-sensitive)." Doh!
Obviously, TB1, the 1 TB USB external drive I'd actually bought as part of a bundle from MacMall when I bought my 27" iMac, and which I had initialized the first day I had the iMac up and running (late November 2009), had somehow gotten initialized as a Case-sensitive drive. How, I don't know, but I suspect the jerk behind the keyboard. Whatever the case, when I created the Terabyte disk image (the drive's original name: when I erased and re-initialized it -- see above -- I renamed it "1TB" for quick identification), the original drive's "Case-sensitive" format was encoded too. So when I tried to drag and drop EVERYTHING from the desktop-mounted volume "Terabyte" to the newly initialized and "blessed" (now THERE's a term from the past!), the system recognized it as an attempt as a total volume backup, and hit me with "The volume [the desktop-mounted volume "Terabyte" -- BB] has the wrong case sensitivity for a backup." And, of course, the reinitialized TB1 was now correctly formatted as NOT "case-sensitive."
Well, that solved the mystery (BTW, Disk Utility identified the unopened Terabyte.dmg as an "Apple UDIF read-only compressed {zlib}, which is why the .dmg file could be copied to ANY volume, case sensitive or not), but it didn't help me with my problem of having to manually move all that data from the desktop-mounted volume "Terabyte" to TB1. I tried to find a way to correct the problem at the .dmg AND opened-volume-from-.dmg level with every disk utility I had, to no avail.
Sorry for the long exposition, but others may trip over this "case-sensitive" rock in the road, and I wanted to make the case as clear as possible.
So my problem remains: other than coal shovel by coal shovel, is there any way to get all the data off this case-sensitive desktop-mounted volume "Terabyte" and onto TB1.
Not that I know whether it would made any difference or not, one of the things that got me into this situation was my inability to get "Time Machine" properly configured so it wasn't making new back-ups every (no lie) 15 minutes.
Philosophical bonus question: what's the need for this "case-sensitive," "NOT case-sensitive" option for disk initialization?
As always, thanks for any help.
Bart Brown

"Am I to understand that you have a case-sensitive volume with data that you want to copy to a case-insensitive volume? And the Finder won't let you do it? If that's what the problem is, the reason should be obvious: on the source volume, you may have two files in the same folder whose names differ only in case. When copying that folder to the target volume, it's not clear what the Finder should do."
Yes, I understand all that... NOW.
What I had (have) is a USB external 1TB drive (henceforth known as "Terabyte") that I bought with my 27" iMac. I formatted, and put a minimal (to make it bootable) system on Terabyte the same day back in late November 2009 that I set up my 27" iMac. Somehow -- I don't know how -- Terabyte got initialized as "case-sensitive." I didn't even know at the time that there WAS such a thing as "case-sensitive" or "NOT case-sensitive" format.
Sunday morning (05/08/11), Drive Pulse, a toolbar-resident utility (that's Part of Drive Genius 3) that monitors internal and external drives for physical, problems, volume consistency problems, and volume fragmentation, reported a single bad block on the volume Terabyte, advising me that it would be best if I re-formatted Terabyte ASAP. I thought I could open Terabyte in a Finder window, Select All, and drag everything on the drive to ANOTHER USB external drive of 2 TB capacity (henceforth known as TB2). When I tried to do that, I got an error message:
"The volume has the wrong case sensitivity for a backup."
First I'd heard of "case sensitivity" -- I'm not too bright, as you seem to have realized.
Oddly enough (to me), I could move huge chunks of data, including a folder of 40GB, from Terabyte to TB2 with no problem.
Then the scenario unfolded per my too-convoluted message: several hours of trying things on my own, including making a .dmg of Terabyte (henceforth to be known as Terabyte.dmg) -- which left me with the exact same problem as described in the previous 4 paragraphs; and my 3 hours on the phone with AppleCare, who at least explained this case-sensitive business, but, after some shot-in-the-dark brainstorming -- tough to do with only one brain, and THAT on the OTHER end of the line -- the very pleasant AppleCare rep and I ended up equally perplexed and clueless as to how to get around the fact that a .dmg of a case-sensitive volume, while not case-sensitive in its "image" form (Terabyte.dmg), and thus able be transferred to TB1 or TB2 with no problems whatsoever, when opened -- either by double-clicking or opening in Disk Utility -- produced a desktop-mounted volume (henceforth known as the volume "Terabyte," the original name of the case-sensitive volume from which TB1.dmg had been made) that had the same case-sensitivity as the original from which it was made.
In the meantime, having gotten the data I needed to save off the physical USB "case-sensitive" volume Terabyte in the form of Terabyte.dmg, I erased and re-initialized the physical USB "case-sensitive" volume Terabyte, getting rif of the case sensitivity, and renaming it TB1. But it all left me back at square one, EXCEPT I had saved my data from the original "Terabyte" drive, and reformatted that drive to a NON- case-sensitive data now named TB1. The confusion here stems from the fact that problem case-sensitive drive, from which I made Terabyte.dmg, was originally named "Terabyte". When I re-initialized it as a NON case-sensitive drive, I renamed it TB1. I'm sorry about the confusing nomenclature, which I've tried to improve upon from my original message -- usual text-communication problem: the writer knows what he has in mind, but the reader can only go by what's written.
So, anyway, I still have the same problem, the desktop-mounted volume "Terabyte" still cannot be transferred in one whole chunk to either my internal drive, TB1, TB2, as the Finder interprets it as a volume backup (which it is), and reads the desktop-mounted volume "Terabyte" as case-sensitive, as the original volume -- from which the disk image Terabyte.dmg was made -- had been at the time I made it.
"As long as that situation doesn't arise, you should be able to make the copy with a tool that's less fastidious than the Finder, such as cp or rsync."
I'm afraid I have no idea what "cp or rsync" are. I'd be happy to be educated. That's why I came here.
Bart Brown
Message was edited by: Bartbrn
Just trying to unmuddy the water a bit,,,

Unique IDs- Case sensitive

Similar Messages

Maybe you are looking for