Ubuntu Server: Cannot Delete File "X", Structure Needs Cleaning

Ubuntu Server: Cannot Delete File "X", Structure Needs Cleaning

I have a game server hosted on my Ubuntu Server 16.04 and out of the blue I cannot start/restart it because of the following file:

-????????? ? ?     ?        ?            ? proceduralmap.3000.1499245715.149.sav

This seems to be the only file in the fs with this situation. Now, the server is a dedicated server purchased from a hosting provider. The drive on which the file resides is a SCSI mounted HDD (/dev/sdb1).

The df -hT output:

Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  3.7G     0  3.7G   0% /dev
tmpfs          tmpfs     744M   81M  663M  11% /run
/dev/sda4      ext4       21G   16G  4.7G  77% /
tmpfs          tmpfs     3.7G   24K  3.7G   1% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs     3.7G     0  3.7G   0% /sys/fs/cgroup
/dev/sda3      ext4      946M  143M  739M  17% /boot
cgmfs          tmpfs     100K     0  100K   0% /run/cgmanager/fs
/dev/sdb1      ext2      985G  265G  670G  29% /storage
tmpfs          tmpfs     744M     0  744M   0% /run/user/1011

What would be the appropriate way of repairing/removing that file? I would prefer repairing it, but removing will do as well. I already ran:

debugfs -w /dev/sdb1

In which I typed:

clri home/steam/serverfiles/server/rustserver/proceduralmap.3000.1499245715.149.sav

I understand, from what I could find on the web, that I would need to run e2fsck, but I understand I would need to unmount the drive first. I wouldn't want to do that just for this one file, if possible.

Thanks!

4

1 Answer

What's up with the "structure needs clearing" error message

The error "structure needs clearing" is the error which file systems (in particular ext4 and xfs) return when they have detected a file system corruption problem. Unfortunately, the only safe thing to do to repair the corruption is to unmount the disk and run e2fsck on the file system. (Technically, you won't need the the -f option because the file system has already detected problems and has marked the file system as being in trouble. So when you run e2fsck it will do a full scan to fix those issues and you don't need the -f option to force a check.)

Chloe Bennett
Author

Chloe Bennett

Chloe Bennett explores the intersection of pop culture, streaming entertainment, digital trends, and contemporary lifestyle. Her weekly commentary reaches thousands of culture enthusiasts.