| To: | Ric Wheeler <rwheeler@xxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS filesystem corruption |
| From: | Julien FERRERO <jferrero06@xxxxxxxxx> |
| Date: | Thu, 7 Mar 2013 14:15:31 +0100 |
| Cc: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mZzQgOJVJoZUbELv9aYvm7mC5Z+CvSbL/dj9vnaCjO8=; b=QzDG/vppeDpaLidbG2R8ud/MN8plP4+5sv65xHk+Eu4Nz/m0/W6GiT8ptkFOfQb0cV ZHzsarn/PSf54PFvMCi+okP5K3nwf7gALcx0t4MBRXp5a6Nyfn8AfWxhR0YFnJF97j5z UjFQPKpiw37kRGXaNgeyhhLnaEgpgBz/FHx0dsOX9GNDwm9oh1yQYw2CjF9NI6hypgDL 3OLRHBs3FNjfWn7iEA872Eyg8HIb3mgmiGeAAv+xd2X1xu1pMyf1bgBY5wi/6HVCUSZp +QkE94WLehaHH8M3F9hQVtHQOVTh/eHIE+s7XpolcbzUuGGVZTdMPCd9Peq7WNyzNv2Y bUZg== |
| In-reply-to: | <5137CD46.6070909@xxxxxxxxxx> |
| References: | <CAPcwv6wZJSBtgF-L6KNSn6N6Y+wUZJFXdbcg+zYRwoaB2sDdjw@xxxxxxxxxxxxxx> <20130306161519.2c28d911@xxxxxxxxxxxxxx> <CAPcwv6wqv0b_CPqDpBfOwVDg23uBi=tpGQSy9XuH2uWS5oVMWQ@xxxxxxxxxxxxxx> <20130306232100.6286f640@xxxxxxxxxxxxxx> <5137CD46.6070909@xxxxxxxxxx> |
> We actually test brutal "Power off" for xfs, ext4 and other file systems. If > your storage is configured properly and you have barriers enabled, they all > pass without corruption. > > What hardware raid cards can do is to hide a volatile write cache. Either on > the raid HBA itself or, even worse, on the backend disks behind the card. > S-ata disks tend to default to write cache enabled and need to be checked > especially careful (sas drives tend to be write cache disabled by default). Write cache is supposed to be disabled on the H/W RAID (according to hdparm) and barrier are correctly enabled since xfs does not report any warning at mount. The odd thing is we never see this with kernel 2.6.18 where barriers weren't yet available. An other difference is the "unwritten extend" that was used to set to 0 by default. Now we cannot change this setting according to an old thread I've found: "unwritten extents on linux are generally a bad idea, this option should not be used.". Unfortunately, the engineer that chose this setting is no longer working with us... |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS IO multiplication problem on centos/rhel 6 using hp p420i raid controllers, Stan Hoeppner |
|---|---|
| Next by Date: | Re: XFS filesystem corruption, Stan Hoeppner |
| Previous by Thread: | Re: XFS filesystem corruption, Ric Wheeler |
| Next by Thread: | Re: XFS filesystem corruption, Ric Wheeler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |