Would you provide more system information, like the output from mount, how you have your Steam Library configured, etc.
Are these the only games that have this error?
Steam library is in ~/.local/share/Steam, but I've tried installing both games to other directories/HDDs with no luck. Both TF2 and Killing Floor install and play fine. If you need any other info I'll be glad to provide it!
>mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) dev on /dev type devtmpfs (rw,nosuid,relatime,size=1989684k,nr_inodes=497421,mode=755) run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) /dev/sda2 on / type xfs (rw,relatime,attr2,inode64,noquota) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) tmpfs on /tmp type tmpfs (rw) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) /dev/sda4 on /home type xfs (rw,relatime,attr2,inode64,noquota) /dev/sda3 on /var type xfs (rw,relatime,attr2,inode64,noquota) /dev/sdb1 on /media/Media type xfs (rw,nosuid,nodev,noexec,relatime,attr2,inode64,noquota,user=luke) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) [email protected]:/home/luke on /home/luke/remotes/musicbox type fuse.sshfs (rw,nosuid,nodev,noexec,relatime,user_id=1000,group_id=100) /dev/sdc1 on /media/Tribute9 type vfat (rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1000,fmask=0137,dmask=0027,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro,user=luke)
Have you tried installing it on a drive that is not xfs (e.g. ext4)?
I don't have any HDDs that use ext4, but I have a flashdrive that does and CS1.6 installed fine there (I'll assume HL1 does too, but I don't have enough free space.) Plays well, too!
Is there anything else I can do to get this working on drives using XFS? I tried using Steam's backup feature to install the game to my XFS drive, but it also refused to work.
I can do any additional tests to help narrow it down!
I'm having trouble reproducing this I'm afraid -- I formatted a drive as xfs and I could install and play HL1 without problems.
However I've put some additional diagnostic information that will be available with the next release we make. When that happens, please try again and paste your updated output. In the meantime, if you can isolate the problem any further (e.g. by trying on more different drives, etc, and seeing if there is any way you can get it working on an xfs drive) it would be appreciated.
Will do!
I'm having trouble on an xfs partition too. I was able to install and run from my / xfs partition, but not the /home xfs partition.
@je-fro would you mind sharing the output of the mount command please.
jeff@texas ~ $ mount
rootfs on / type rootfs (rw)
/dev/sdf3 on / type xfs (rw,noatime,attr2,inode64,noquota)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=763010,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib64/rc/sh/cgroup-release-agent.sh,name=openrc)
cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
/dev/sdh1 on /home type xfs (rw,inode64)
/dev/md0 on /home/jeff/media type xfs (rw,inode64)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nodev,noexec,nosuid)
jeff@texas ~ $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 186G 66G 121G 36% /
/dev/sdf3 186G 66G 121G 36% /
tmpfs 3.0G 912K 3.0G 1% /run
udev 10M 0 10M 0% /dev
shm 3.0G 3.0M 3.0G 1% /dev/shm
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
/dev/sdh1 2.5T 1.6T 896G 65% /home
/dev/md0 11T 1.6T 9.4T 15% /home/jeff/media
jeff@texas ~ $
Is anyone running steam with an xfs /home partition?
Yep!
What are your mount options?
How did you install steam?
Did you run into any difficulties along the way?
rw,relatime,attr2,noquota 0 1
Installed via Pacman if I remember correctly.
Every game except the Goldsrc ones have worked so far.
What is your output from "mount"?
What is printed in the console when you launch "steam"?
Thanks!
Now I'm getting this:
jeff@texas ~ $ steam
Running Steam on gentoo 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1367621987_client)
Installing breakpad exception handler for appid(steam)/version(1367621987_client)
Installing breakpad exception handler for appid(steam)/version(1367621987_client)
unlinked 0 orphaned pipes
removing stale semaphore last operated on by process 2753 with name 0eBlobRegistryMutex_C27AE43A53E57CB77A9FC7B7D1AD70BE
removing stale semaphore last operated on by process 2753 with name 0eBlobRegistrySignal_C27AE43A53E57CB77A9FC7B7D1AD70BE
removing stale semaphore last operated on by process 2753 with name 0emSteamEngineInstance
removing stale semaphore last operated on by process 2753 with name 0eSteamEngineLock
Installing breakpad exception handler for appid(steam)/version(1367621987_client)
[0512/171752:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[0512/171752:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/tier1/../tier1/utlbuffer.cpp (221) : Assertion Failed: nSize != 0
Assert( Assertion Failed: nSize != 0 ):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/tier1/../tier1/utlbuffer.cpp:221
Installing breakpad exception handler for appid(steam)/version(1367621987_client)
Uploading dump (out-of-process) [proxy '']
/tmp/dumps/assert_20130512171753_1.dmp
ILocalize::AddFile() failed to load file "resource/vgui_english.txt".
ILocalize::AddFile() failed to load file "resource/overlay_english.txt".
Failed to load overlay localization file.
Finished uploading minidump (out-of-process): success = no
error: HTTP response code said error
@je-fro have you tried installing a new steam from fresh, ie via packages?
This is probably due to inode64 mount option (which is really required on large XFS volumes). I glad I have not yet converted my 44TB JFS file-system to XFS (I already migrated my 84TB to XFS).
XFS inode numbers have to due with their physical location on the file-system (I believe to save seeks or something) but because of this you will have inode numbers that are outside of 32-bit address space. In this case a 64-bit stat needs to be used (which would happen natively if steam was 64-bit). I also made this comment on the 64-bit issue:
https://github.com/ValveSoftware/Source-1-Games/issues/906
As a possible issue with steam and why it should be 64-bit and low-and-behold a quick google search made me find this issue.
A similar issue happened in the past (which I reported and was corrected) that cause available disk space to fail causing updates to fail if you had > 2 TiB of free space. Again it would have been fine on a 64-bit binary.
Just to update as well the guy who reported issues likely did not have problems with everything as he was using 1.6TB of data. Not necessarily going to be a problem unless the metadata/inodes are actually written past the 2 TiB barrier which likely wont happen that often when your used space is under the 2TiB barrier. Definitely going to be a problem for me:
root@dekabutsu: 08:06 PM :~# df -H /data /data2
Filesystem Size Used Avail Use% Mounted on
/dev/sdd1 44T 39T 4.8T 90% /data
/dev/sde1 84T 65T 20T 77% /data2
This has broken almost my entire game library now, and it definitely isn't just GoldSrc anymore. According to the referenced issue above the beta was supposed to address this, but I still have issues. My library is slowly being disabled. Is this being worked on still?
They haven't fixed it yet and whether its goldsrc has nothing to do with it. I haven't played steam at all since I moved over to XFS a few weeks ago =(. Issue #2610 will probably be 'closed' or 'resolved' and not 'open' when they actually fix it in the code and then probably would be in the next release after that.
We've made some changes to use stat64 that'll go out in a future Steam client beta (don't have a specific time frame).
I assume that is for steam (client) and all steam games? Looking forward to being able to use steam again...
The changes are in the Steam client, which should be where most of your problems are. The games are separate and unaffected, unfortunately.
In other words, if your problem is installing or updating games you should see improvements since that's done by the client. If your problem is a failure while a game is running that's a separate issue.
Well just in the steam client is possibly worthless? I assume games have to read in config files and other data which are going to fail a file-system that uses 64-bit inodes?
File open should work fine regardless, this issue only affects things like stat that can't return proper info. Games may use those in critical paths or may not, it will depend on the game and the action.
Well if you happen to find out when this actually gets put in a release please let me know so I can test and see if things work properly.
Unfortunately I think its not going to work on a lot of games. I know when I moved stuff over to /dev/shm (to get 32-bit inodes) running a game like counter-strike: source didn't have any fonts in it (probably because the font files are >32 bit inode values so I think games will need to be modified too.
It seems like if steam is so intent on not building 64-bit versions of the games then they should at least have the proper support for 64-bit/large file-systems. >2 TiB is pretty common these days...
You're right that games are an entirely separate problem, but the latest Steam client beta (just came out today, 8/8/2013) should allow install at least.
Closing pending more feedback. NOTE: game bugs should be filed for games themselves.
I still can't get steam to run at all on inode64. Maybe chicken and the egg thing? Is there anyway to get the steam.deb updated on the site to a newer version that has this fix in it?
Nothing extracted yet.
Both HL1 and CS1.6 fail to install with the following message:
Installation drive is using XFS, if that has anything to do with it.