| To: | Asdo <asdo@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Any on-disk format changes recently? |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 24 Nov 2009 17:22:30 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4B0C2E46.1040509@xxxxxxxxxxxxx> |
| References: | <4B0C2E46.1040509@xxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.21 (X11/20090320) |
Asdo wrote: > Dear XFS people > I am tracking a nasty bug for which I would need to regress the kernel > version from 2.6.31 down to 2.6.28 or maybe even 2.6.24. > I have to do this on an important fileserver full of important data on > XFS filesystems which were created on 2.6.31. > I also need to *write* to the XFS filesystems after regressing the kernel. > Do you see any problems with this? Have there been on-disk format > changes for XFS since 2.6.24 that could trigger data loss? (or with much > minor concern, fail the mount?) Nothing about the xfs disk format should cause problems when bouncing between .24 and .31 -Eric > Thank you > Asdo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH XFS] Fix error return for fallocate() on XFS, Jason Gunthorpe |
|---|---|
| Next by Date: | Re: [PATCH XFS] Fix error return for fallocate() on XFS, Eric Sandeen |
| Previous by Thread: | Any on-disk format changes recently?, Asdo |
| Next by Thread: | [PATCH XFS] Fix error return for fallocate() on XFS, Jason Gunthorpe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |