Re: ffs corruption

[Emmanuel Dreyfus <manu%netbsd.org@localhost>]

On Wed, May 24, 2017 at 07:29:44PM +0000, Emmanuel Dreyfus wrote:
> Other VM on the machine have no problems, which suggests it is not a disk
> problem.

Update: This morning I hit the same problem onanother VM from the
same physical machine:
$ ls -l /usr/lib/libfetch.so.3                         
ls: /usr/lib/libfetch.so.3: Bad file descriptor

Now that strongly hints for a hardware problem. This get somehow off-topic,
but what is the right list for that?

Disk or SATA controller? SMART status are good, and the only speciall thing
the dom0 reports is from xl dmesg:
(XEN) d22 attempted to change d22v1's CR4 flags 00002660 -> 00000600
(XEN) d23 attempted to change d23v1's CR4 flags 00002660 -> 00000600
(XEN) d24 attempted to change d24v1's CR4 flags 00002660 -> 00000600
(XEN) d25 attempted to change d25v1's CR4 flags 00002660 -> 00000600
(XEN) d26 attempted to change d26v1's CR4 flags 00002660 -> 00000600


-- 
Emmanuel Dreyfus
manu%netbsd.org@localhost