[PVE-User] Again trouble, but this time with ext4/trim...

[Marco Gaiarin]

Mandi! Fabian Grünbichler
  In chel di` si favelave...

> are you sure this storage box supports fstrim at all? thin provisioning
> and trim/discard often go together, but they don't have to..

Whai i can say is:

1) In the past, i've done 'direct iSCSI assignment' to some VM, eg the
 VM mount the iSCSI volume, and i can trim them flawlessy.

2) in autumn, i've created a new set ov VMs, where i've abandoned
 direct iSCSI mount and i use PVE volumes instead. Clearly, i've done
some test for trim/discard, verifying that space get correctly
reclaimed.
After some weeks, i've suffered ext4 corruption as now.

3) in december i've upgraded the cluster to PVE 5; filesystem
 corruption desappear.

4) some weeks ago i was forced ot reboot the cluster (to change an
 UPS), and FS corruption reappeared.


For now, i've removed the 'discard=on' options from volumes that have ext4
FS.

The crazy things is that volumes formatted in XFS, residing on the
same SAN, seems does not suffer at all of FS corruption.


If i can do some test, please, say me.


> quick googling only showed some vmware specific integration to 'reclaim
> no longer used space of thin provisioned volumes', but no explicit
> mention of discard support.

Ahem, but trim/discard are not the same things?

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''          http://www.lanostrafamiglia.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
      http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)