| To: | Julien FERRERO <jferrero06@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS filesystem corruption |
| From: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
| Date: | Wed, 6 Mar 2013 23:21:00 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CAPcwv6wqv0b_CPqDpBfOwVDg23uBi=tpGQSy9XuH2uWS5oVMWQ@xxxxxxxxxxxxxx> |
| Organization: | Intellique |
| References: | <CAPcwv6wZJSBtgF-L6KNSn6N6Y+wUZJFXdbcg+zYRwoaB2sDdjw@xxxxxxxxxxxxxx> <20130306161519.2c28d911@xxxxxxxxxxxxxx> <CAPcwv6wqv0b_CPqDpBfOwVDg23uBi=tpGQSy9XuH2uWS5oVMWQ@xxxxxxxxxxxxxx> |
Le Wed, 6 Mar 2013 17:16:31 +0100 vous Ãcriviez:
> I don't think the H/W RAID is
> the issue since we have the same corruption with other setup without
> H/W RAID.
HW RAID may exacerbate the problem. XFS is absolutely, definitely not
"brutal power off" safe. All linux systems from this century are
perfectly able to turn themselves off properly at a single press of the
power button; the only safe options are educating the users or mounting
the filesystem read-only.
And yes, the ls garbled output is caracteristic of a filesystem
corruption.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@xxxxxxxxxxxxxx>
| +33 1 78 94 84 02
------------------------------------------------------------------------
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Pathological allocation pattern with direct IO, Ben Myers |
|---|---|
| Next by Date: | Re: XFS filesystem corruption, Ric Wheeler |
| Previous by Thread: | Re: XFS filesystem corruption, Ric Wheeler |
| Next by Thread: | Re: XFS filesystem corruption, Ric Wheeler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |