|To:||Renaat Dumon <renaat.dumon@xxxxxxxxxx>|
|Subject:||Re: XFS corruption on 2.4.28|
|From:||Eric Sandeen <sandeen@xxxxxxx>|
|Date:||Thu, 03 Nov 2005 10:34:15 -0600|
|User-agent:||Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720)|
Renaat Dumon wrote:
Hi Eric, I've put the parameters back, and had a contact with one the "platform" guys of my vendor. When I asked if he could think of something to explain the fact that apparently only the small .db files were affected, he wasn't sure. But he did mention these files where designed to be this small, so they could be stored on disk in meta-data only. While I don't know what this really means, I thought I'd run this by you to see if maybe it could isolate the issue a little bit further.
It means that for very small files, the file data can be stored in the disk inode itself, rather than in an extent outside the inode. Not a bad idea.
If you're in touch w/ the vendor, perhaps you can work with him to try a stock 2.4.28 kernel, see if the problem persists.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: XFS information leak during crash, Alan Cox|
|Next by Date:||Re: XFS information leak during crash, Theodore Ts'o|
|Previous by Thread:||Re: XFS corruption on 2.4.28, Eric Sandeen|
|Next by Thread:||Re: 18.104.22.168 amd64: XFS: xlog_recover_process_data: bad clientid, linux|
|Indexes:||[Date] [Thread] [Top] [All Lists]|