The game will crash upon start up if you install it on a drive, or partition 1 and 1/2 to 2 TiB or larger formated with XFS.
Especially if it is a Raid drive.
Which sucks because raiding multiple discs of that size is the easiest and cheapest form of adding storage for linux users.
The game does not seem to like 64bit inodes. https://en.wikipedia.org/wiki/Inode
And will segfault upon start up as it tries to look for it's files looking for them, and not finding them because it seems to be coded for 32bit inodes, used on formated discs less than 2TiB in size.
edit: specific error.
Borderlands2: segfault at 7 ip 00000000f70a6658 sp 00000000ffcf1670 error 4 in libc-2.19.so[f7030000+1a0000]
Not on the part of the Borderlands developers, mind you.
It's epicly bad on the part of whoever designed that aspect of the way Linux handles file systems: you'd think a detail such as 32-bitness vs 64-bitness of an inode, which is pretty much meant just as a reference to an open file, would be abstracted away...
Normally it is, this is the only game in my library that seems to be picky about this.
But, do any Windoze users have this issue?
I run Win7 Home Premium 64 bit, no issues, Windoze Uplate patched those issues with large drives I guess because it works. I DO have issues with some old games, had to use unofficial patch for Fallout 3, Morowind is unstable, but no drive issues.
Ah good for you then. Still this is besides the point, this is about the linux version of the game not windows.
Also it more shows the quality of the port rather than the os as everything else seems to have no trouble working.
I guess the point I was going for is, would that not be an OS thing? Why would a game have anything to do with the file system?
because there are two ways to access files on a journaled file system like xfs/ext3 & 4, jfs, ntfs, hfs+ etc.
The first is to use the inode/fileid location, the second is to use the realitive path location. They coded the game to use the former. This is bad practice *nix wise because data is so easially movable in the *nix world. A program should not care what file system it's on as long as the relative path is intact.