To begin, I will state that I have fixed the problem for my MacBook. I wanted to share my story, in the hope that I can provide some reassurance if anyone else finds they cannot boot their OS, that there is a solution, and you don't need Apple support if you are willing to experiment. If you have your data backed up, there's not too much damage you can do (I think).
I had the same problem yesterday as what others have mentioned on here when I started using my new MacBook Pro on Yosemite. During the initial configuration on first boot, I left FileVault enabled. During the encryption process after startup, it paused indefinitely. I followed the steps others suggested on here - resetting PRAM, clearing disk permissions, repairing disk etc. with varying order. None of that worked. I later made a Time Machine backup onto my external HDD and attempted a restore via Recovery (Cmd+R). This failed quickly, but I can't remember what the error was. I think it had something to do with not being able to modify an encrypted disk, even though it said it would turn off FileVault. Presumably this is because it hadn't finished, which is why you can't stop it in the UI either. This had a bad consequence in that the partition was deleted when I inspected in Disk Utility. I was also unable to create a partition as the options were greyed out. The Disk Utility was not able to modify the Macintosh HD drive, other than a Repair Disk button which didn't help.
After some research, I came across a post online which explained how to delete the CoreStorage volume without the need to decrypt the drive. This is useful if the encryption process messes up. I ran the command:
diskutil cs list
This produces a list of the volumes. The top Logical Volume Group was my drive. Be sure to find the correct one! I copied the UUID (long number) into my clipboard for use with the next command:
diskutil cs delete MyUUID
where MyUUID is that number I copied into my clipboard.
After running that, it reformatted the CoreStorage volume into an unencrypted (HFS+) one, with a blank partition. This looked promising.
Afterwards, I booted into Recovery again and attempted the restore from Time Machine again. This time it was successful and the drive booted up with FileFault turned off. I decided, since I know how to fix the problem if it happens again, I would be a daredevil and attempt the encryption again. This time, the encryption was also successful, completing in less than 1 hour. I decided not to do any other tasks while that happened.
This experience was rather stressful, especially since it happened within a few hours of booting up the first time. However, it was an educational task for me, coming from a Windows background. There is clearly some major bug in FileVault when run in a Yosemite environment. I don't know if it affects everyone and if it can go wrong again, but I will be interested to see if Apple come up with a patch fix.