Le 15/11/2018 à 12:35, Marco Gaiarin a écrit :
> Mandi! Mark Schouten
> In chel di` si favelave...
>
>> Obviously, a misbehaving SAN is a much better explanation for
>> filesystemcorruption..
> Sure, but:
>
> a) errors start a bit befose the SAN trouble
>
> b) this is the only VM/LXC that have troubles
>
> c) i've tried to unmount, reformat and remount a disk/partition (was
> the squid spool) and errors come back again.
>
>
> It is really strange...
Not that strange. It's expected to have FS corruption if they resides on
a thin provisionned volume, which itself has no space left. Lucky you
only had one FS corrupted.
++
--
Logo FWS
*Daniel Berteaud*
FIREWALL-SERVICES SAS.
Société de Services en Logiciels Libres
Tel : 05 56 64 15 32
Matrix: @dani:fws.fr
/www.firewall-services.com/
_______________________________________________
pve-user mailing list
[email protected]
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
