24 Jun
2016
24 Jun
'16
5:46 a.m.
On Friday 24 June 2016 02:11:31 deloptes wrote:
Steven D'Aprano wrote:
No raids on the property, Steven.
Thanks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
On Fri, Jun 24, 2016 at 12:22:18AM -0400, Gene
Heskett wrote:
Or unsynced RAID cache - I had it once. But why should a powerdown as unceremonious as
pulling the plug,
have deleted /usr/bin/X? It doesn't grok at this site.
File system corruption?
What file system do you have? If it is something with a journal
(ext4, for example) I would be surprised. If it is something
experimental or less reliable (btfs, reiserfs?) then I wouldn't be
surprised.
All file systems can lose data if you interrupt them while updating
the file system, but some are more resiliant than others. I tend to
prefer the good old ext3 or ext4 standby over flashier, faster but
less resiliant newer file systems, and older, unjournaled file
systems like ext2.
Have a look inside /lost+found (assuming /usr/bin is in the /
partition) and see if there's anything there. You may find all your
X files, and more, given generic names. Or you may find nothing at
all.