Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TAKE\s+952214\s+\-\s+log\s+recovery\s+compat\s+on\s+32\/64\s+bit\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*TAKE\s+952214\s+\-\s+log\s+recovery\s+compat\s+on\s+32\/64\s+bit\s*$/: 8 ]

Total 8 documents matching your query.

1. TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Timothy Shimmin <tes@xxxxxxxxxxxxxxxxxxxxxxx>; Date: Wed, 24 May 2006 15:20:47 +1000 (AEST); The change here is to allow a dirty log XFS filesystem be replayed on a same endian machine but of different word size (eg. i386 and x86_64). --Tim inode items and EFI/EFDs have different ondisk form; /archives/xfs/2006-05/msg00043.html (9,773 bytes)
2. Re: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Shailendra Tripathi <stripathi@xxxxxxxxx>; Date: Wed, 24 May 2006 12:00:57 +0530; Hi Tim, There is another problem in XFS recovery on non-XFS native endian machines. xlog_recover_do_inode_buffer () { .... logged_nextp = (xfs_agino_t *) ((char *)(item->ri_buf[item_index].i_addr) +; /archives/xfs/2006-05/msg00044.html (14,545 bytes)
3. Re: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Timothy Shimmin <tes@xxxxxxx>; Date: Thu, 25 May 2006 15:42:48 +1000; Hi Shailendra, That's no good. Okay, I had a better look at the code, and I see what you mean. The di_next_unlinked field is always stored endian converted. It has to be converted to native only when; /archives/xfs/2006-05/msg00046.html (10,968 bytes)
4. RE: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: "Mike Gigante" <mg@xxxxxxx>; Date: Thu, 25 May 2006 19:16:55 +1000; Also, it would be good to provide test cases which you used to reproduce the initial problem and verify the fix was correct. Mike; /archives/xfs/2006-05/msg00047.html (8,054 bytes)
5. TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Timothy Shimmin <tes@xxxxxxxxxxxxxxxxxxxxxxx>; Date: Wed, 24 May 2006 15:20:47 +1000 (AEST); The change here is to allow a dirty log XFS filesystem be replayed on a same endian machine but of different word size (eg. i386 and x86_64). --Tim inode items and EFI/EFDs have different ondisk form; /archives/xfs/2006-05/msg00143.html (9,773 bytes)
6. Re: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Shailendra Tripathi <stripathi@xxxxxxxxx>; Date: Wed, 24 May 2006 12:00:57 +0530; Hi Tim, There is another problem in XFS recovery on non-XFS native endian machines. xlog_recover_do_inode_buffer () { .... logged_nextp = (xfs_agino_t *) ((char *)(item->ri_buf[item_index].i_addr) +; /archives/xfs/2006-05/msg00144.html (14,545 bytes)
7. Re: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: Timothy Shimmin <tes@xxxxxxx>; Date: Thu, 25 May 2006 15:42:48 +1000; Hi Shailendra, That's no good. Okay, I had a better look at the code, and I see what you mean. The di_next_unlinked field is always stored endian converted. It has to be converted to native only when; /archives/xfs/2006-05/msg00146.html (10,968 bytes)
8. RE: TAKE 952214 - log recovery compat on 32/64 bit (score: 1): Author: "Mike Gigante" <mg@xxxxxxx>; Date: Thu, 25 May 2006 19:16:55 +1000; Also, it would be good to provide test cases which you used to reproduce the initial problem and verify the fix was correct. Mike; /archives/xfs/2006-05/msg00147.html (8,054 bytes)

Current List: 1 - 8
Page: [1]