I have a text file that apparently was corrupted somehow.If I attempt to read the file using vim, less, cat, or cp, the process spawned hangs. The System Monitor shows a status of Uninterruptible and a waiting channel wait_on_page_bit_killable.I cannot stop the process with Ctrl-X or Ctrl-Z, only by killing it in the System Monitor.Oddly, this does not happen if I try to open the file with pluma: Pluma can't open the file, just cycling the loading indicator, but the process has normal status and responds to commands. It does happen if I use okular, so pluma must be doing something special.What happened? Luckily, it's not vital to me to recover this particular file. It's a text file that was being used in my python code, so I definitely want to know what I might have done to cause this.Possibly-useful information: I am running Arch, uname -r gives me 4.9.11-1-ARCH. My filesystem is ext4. Next, I will reboot and report back if anything changes.Update: After rebooting and running fsck from a USB, I can open and read the file just fine. I ran$ fsck -r /dev/sda2/dev/sda2: clean, XX/YY files, XX/YY blocks/dev/sda2: status 0, res 3016, real XX, user XX, sys XX
Reading text file hangs with wait_on_page_bit_killable
files;filesystems;kernel;process