| To: | stan@xxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS filesystem corruption |
| From: | Julien FERRERO <jferrero06@xxxxxxxxx> |
| Date: | Mon, 11 Mar 2013 10:25:13 +0100 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, Ric Wheeler <rwheeler@xxxxxxxxxx>, 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=UwRG4UhdAuwVIB4HAsa+vsifzmDz0VJiSDNXgZGAM0I=; b=sQLhkzfueKn9ZHzlBGd8SV8kdA+Nr1EKWvS4blkatFNAEJYbERJXSmwCrbL154Kwb5 Z38MY25JWtQfVZdiFBfKqb6I/RlsgryaBWRoncin0+96UqWsDinpaZnjOVZ0JcwlOT/6 SKyfnVnxory2n3d1rTCEztRx0cfRPXuMJcNhAKzm9CHtmV5UGab0qnwlMHoD8M2QYqhf 3erftsXqB4oBsBhQ1REhxHzFtGd4xzownJTv+O9mqSyyurVPff8CVpVJsLXXXnJ+5ZND HfTPx5iTIBLQRhKs9hfuG++ODeBOKvGZEma6IF55IUMhJDXiR4Td0mNhdPAPGbt3APKz JPpg== |
| In-reply-to: | <513D1D51.7010905@xxxxxxxxxxxxxxxxx> |
| References: | <CAPcwv6wZJSBtgF-L6KNSn6N6Y+wUZJFXdbcg+zYRwoaB2sDdjw@xxxxxxxxxxxxxx> <20130306161519.2c28d911@xxxxxxxxxxxxxx> <CAPcwv6wqv0b_CPqDpBfOwVDg23uBi=tpGQSy9XuH2uWS5oVMWQ@xxxxxxxxxxxxxx> <20130306232100.6286f640@xxxxxxxxxxxxxx> <5137CD46.6070909@xxxxxxxxxx> <5139A3B6.3040805@xxxxxxxxxxxxxxxxx> <5139D792.4090304@xxxxxxxxxx> <513A350A.508@xxxxxxxxxxxxxxxxx> <20130309091152.GH23616@dastard> <513B84AD.2000603@xxxxxxxxxxxxxxxxx> <20130310224536.GK23616@dastard> <513D1D51.7010905@xxxxxxxxxxxxxxxxx> |
> > Ok, see, this is odd part here. The OP didn't seem to have this > metadata corruption issue with the old 2.6.18 kernel, at least I think > that's the one he mentioned. Then he switched to 2.6.35. IIRC there > were a number of commits around that time and some regressions. I also > recall 2.6.35 is not a long term stable kernel. I'd guess there were > reasons for that. So, I'm wondering if there was a bug/regression > relating to XFS metadata in 2.6.35 corrected in .36 or later and simply > not backported. Seems to ring a bell, vaguely. I have no idea > where/how to search for such information. > That is the main reason I asked. I google for regression / issue with XFS in 2.6.35 but I didn't find anything. My hope was that someone from this mailing list would remember it (if such a regression did exist of course). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfs: Remove obsoleted m_inode_shrink from xfs_mount structure, Jeff Liu |
|---|---|
| Next by Date: | Re: XFS filesystem corruption, Stan Hoeppner |
| Previous by Thread: | Re: XFS filesystem corruption, Dave Chinner |
| Next by Thread: | Re: XFS filesystem corruption, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |