You are building on a case-insensitive filesystem. - Nexus 6 Developer Discussion [Developers Only]

OK so have had this issue for 2 days and am getting past the point of frustration I can think clearly. A few days ago I lost my second drive. For the most part have a smaller SSD with Ubuntu installed on it and is ware my ccache directory is kept. With that said had always had another much larger sata HDD I used for storing Source code and building. At times have had 10 or 15 different variations of source. I have my reasons but comes down to really is only trash when needed because like looking back at things I may not have committed or other reasons.
Anyhow my issue is after loosing a drive I broke out an old 2TB drive I ran Ubuntu on back a few years back before getting my SSD when I had everything on one drive. This drive had 10.04 on it and would still boot if I unplugged my SSD. So first I just deleted what was on the drive downloaded AOSP and when I ran make clean I received.
build/core/main.mk:120: ************************************************************
build/core/main.mk:121: You are building on a case-insensitive filesystem.
build/core/main.mk:122: Please move your source tree to a case-sensitive filesystem.
build/core/main.mk:123: ************************************************************
build/core/main.mk:124: *** Case-insensitive filesystems not supported. Stop.
Thought it odd ass it was Ext4 and had Linux running from it so decided I would just reformat Ext4 using Gparted as also wanted to rename the drive. After reformatting and again downloading android-6.0.1 again received the same "Case-insensitive filesystems not supported" error. I have done every case sensitive check I can find and they all come back that the drive is Case Sensitive. I have no issue compiling Kernels but cant figure out for the life of me why it thinks I am trying to compile AOSP on a case sensitive drive. I have been using Google for two days now and cant seem to find anything so thought I would try here. Usually after posting about an issue I will shortly after realize my own stupidity. Its all good I am willing to look like a dumb ars if it means getting back on track. Only other thing I can come up with is that something is wrong with the drive but shows no sign that is the case.

---

Please provide output of "sudo mount" and "cat /etc/fstab"

---

doitright said:
Please provide output of "sudo mount" and "cat /etc/fstab"
Click to expand...
Click to collapse
sudo mount
/dev/sdc1 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,default_permissions,allow_other)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=chairshot215)
/dev/sda1 on /media/chairshot215/drive3 type ext4 (rw,nosuid,nodev,uhelper=udisks2)
/dev/sdb1 on /media/chairshot215/40934518-ac79-4226-9930-b6ede601f16f type ext4 (rw,nosuid,nodev,uhelper=udisks2)
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=f576335c-5df7-4d86-9fdf-90bb7b45e89b / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=6200c094-f594-4a29-8809-70b3b1cfc00c none swap sw 0 0
Let me know if this helps and thanks for responding.

---

The things just been acting up in general which is scary. The entire rig was donated a few years back by a hanfull of developers and a few others. Is a dell T5400 Workstation. Long story but decided to try and learn something at the same time a handful of devs had been trying to port ICS to the Motorola Triumph a foxcon phone released by like 5 companies all over the world and had figured out a bunch of stuff looking at those devices for the most part via Google Translate. Next thing Got the tower then two quad core processors 16g of Ram cards and a bunch of odds and ends I never would have been able to afford as was using a New Egg bare bones self built jamer previously and took build time from like 12 hours to about half hour 45 minutes. I have a hart attack every time something starts acting funny but thankfully ends up being something like needing a new graphics card or Ram stick. graphics card / power supply was scary as had occurred during a power surge that blew my surge protector and for a small bit thought the entire thing was fried as some smoke was coming out. Think I almost cried well actually I did. Otherwise is the only donations I have ever received and am so thankful as who knows what I would be doing with my spare time. Just cant believe I am currently spending so much time on this case sensitive issue. I have put in second drives since making the Linux switch as at first set to duel boot with one Windows drive and one for Linux till I found I had gone months without booting into Windows and formatted the Windows drive never looking back but again never had any issues with case sensitivity especially using a drive I had used for building in the past. Had always been an extremely simple process. Any drive not already used for Linux would format in Ext4 and if had been a Linux drive in the past would really just delete the contents maybe change ownership if needed. Admittedly though with build environment never sought out knowledge unless needed as always had a project of some sort I had been more enthusiastic about. However adding to the frustration because of storage $$ reasons at one point was building with the source located on a USB drive with the output directory and modest size ccache going to my small SSD and was building in a reasonable time. The frustrating part was it had taken the time needed to download AOSP on the USB drive to work it all out and cant figure out a cure for this Case Sensitive issue to save my life. That said not being able to identify the cause I have not tried just reinstalling first on the SSD as have spent enough time trying to fix the problem may as well try starting from scratch all the way through enough as it dreads me going over everything as I constantly forget something thinking I am done then remember I did not set a text editor or the dam ssh key. Am I the only one who every single set up forgets to set up that dam key every single time??

---

I can't read that last reply, needs way more organization before I'm willing to attempt it. Something stands out to me;
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,default_permissions,allow_other)
What is that, besides something obviously related to vmware? Is this some kind of virtual machine? What is the path to the build root?

---

doitright said:
I can't read that last reply, needs way more organization before I'm willing to attempt it. Something stands out to me;
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,default_permissions,allow_other)
What is that, besides something obviously related to vmware? Is this some kind of virtual machine? What is the path to the build root?
Click to expand...
Click to collapse
Sorry that last post was more a late night frustration rant. I just got it working but not exactly sure how. For the most part installed Ubuntu on the drive again as the drive was an older drive I was running Ubuntu on before purchasing an SSD. After the installation I used gparted and unmounted and changed the drive label name. Next changed the permissions on the drive to match those from the Ubuntu installation on my SSD and put all the files from installing Ubuntu on the drive in the trash. After that downloaded AOSP and everything is building now without any issues.
Otherwise had not used a virtual machine. The set-up was with two drives. One was an 80gb ssd that I was running Ubuntu and the second drive was just for building. I was using a 256gb ssd as my building drive but it stopped reading so I used an older 2TB HD that I had used in the past before I had an SSD that had I believe 10.4 installed on it and my issues had started when I replaced the broken SSD with my old HD from back in the days of 10.4. Is strange though because I essentially made the same steps that ended up solving the issue among others that had not worked the probably 5 times before. Overall I am just happy I am back up and building again.
Boya my first successful build since replacing my build drive.
#### make completed successfully (01:27:36 (hh:mm:ss)) ####
Do have an opinion question though. I have about 30g left on my SSD. Do you think it would speed things up any if the ccache was on the SSD? Figure would still be limited to the write speed of the Sata HD but wondering if I may see any boost due to the read speed of the SSD from using ccache. I know they recommend like 50g on the ccache size but I have checked the size in the past and unless I am building 3 pretty different Roms like sharing the same ccache with different versions of AOSP & CM the size usually is in the 10/15gb range for just compiling AOSP with in-line Kernel building set up. Can take the time to just test it myself but till tax return a comith I am stuck building from the older 2TB HD from 2009.
Thanks for looking over things and trying to help out.