What fs type is /usr/include/ on?
Most times those turn out to be filesystem corruption of one kind
or another. What is really means is that the kernel can't make sense out
of what it finds in the dinode; there can be valid reasons for that but
fs corruption is the common one.
On
On Sat, 15 Feb 2014 22:34:11 +0200
Alan McKinnon alan.mckin...@gmail.com wrote:
What fs type is /usr/include/ on?
Most times those turn out to be filesystem corruption of one kind
or another. What is really means is that the kernel can't make sense
out of what it finds in the dinode; there
This is not at all unlikely - the virtual machine is running in a windows
host that was created by restoring from backups after a drive failed. Also,
the 'new' disk it was restored to is not really a new disk at all.
I am not really knowledgeable about virtual machines at all - would
deleting
On 16/02/2014 02:20, Will Hopper wrote:
This is not at all unlikely - the virtual machine is running in a windows
host that was created by restoring from backups after a drive failed. Also,
the 'new' disk it was restored to is not really a new disk at all.
I am not really knowledgeable
