Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*REVIEW\:\s+xfs

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*REVIEW\:\s+xfs_reno\s+\#2\s*$/: 33 ]

Total 33 documents matching your query.

1. Re: REVIEW: xfs_reno #2 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 3 Jun 2008 16:34:57 -0400; What happened to xfs xfs_reno patch? While the swapino functionality would be nice to have I can't think of a reason to not have the current code in xfsprogs.; /archives/xfs/2008-06/msg00033.html (7,068 bytes)
2. Re: REVIEW: xfs_reno #2 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Tue, 3 Jun 2008 16:34:57 -0400; What happened to xfs xfs_reno patch? While the swapino functionality would be nice to have I can't think of a reason to not have the current code in xfsprogs.; /archives/xfs/2008-06/msg00493.html (7,068 bytes)
3. Re: REVIEW: xfs_reno #2 (score: 1): Author: Ruben Porras <ruben.porras@xxxxxxxxxxx>; Date: Thu, 06 Mar 2008 17:10:35 +0100; Am Donnerstag, den 04.10.2007, 14:25 +1000 schrieb Barry Naujok: +static int +process_slink( + bignode_t *node) +{ + int i = 0; + int rval = 0; + struct stat64 st; + char *srcname = NULL; + char *pna; /archives/xfs/2008-03/msg00063.html (10,132 bytes)
4. Re: REVIEW: xfs_reno #2 (score: 1): Author: Ruben Porras <ruben.porras@xxxxxxxxxxx>; Date: Thu, 06 Mar 2008 17:11:46 +0100; Am Dienstag, den 20.11.2007, 12:36 +1100 schrieb David Chinner: Hello again, I have this week again time to at xfs_reno and xfs_swapino and xfs_swap_extents functions. I adapted xfs_reno to use these; /archives/xfs/2008-03/msg00064.html (10,105 bytes)
5. line 1150 of file fs/xfs/xfs_trans.c (score: 1): Author: @xxxxxxxxx; Date: Thu, 06 Mar 2008 17:10:35 +0100; alize_perag() to set up pag->pagi_inodeok, pag->pagf_metadata and mp->m_maxagi which are used by the allocator.... Much better. Cheers, Dav; /archives/xfs/2008-03/msg00452.html (10,132 bytes)
6. s/xfs_trans.c (score: 1): Author: xxxxxxxxx>; Date: Thu, 06 Mar 2008 17:11:46 +0100; lesystem shutdown when its 99% full (according to df -k): /data# mkdir test mkdir: cannot create directory `test': No space left on device; /archives/xfs/2008-03/msg00453.html (10,105 bytes)
7. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Fri, 16 Nov 2007 17:04:09 +1100; Barry Naujok wrote: A couple changes from the first xfs_reno: - Major one is that symlinks are now supported, but only owner, group and extended attributes are copied for them (not times or inode att; /archives/xfs/2007-11/msg00167.html (10,245 bytes)
8. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Fri, 16 Nov 2007 17:20:28 +1100; Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directory. This may not be that easy though. Really?; /archives/xfs/2007-11/msg00169.html (8,851 bytes)
9. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Mon, 19 Nov 2007 10:13:43 +1100; Timothy Shimmin wrote: Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directory. This may not be th; /archives/xfs/2007-11/msg00180.html (9,247 bytes)
10. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Mon, 19 Nov 2007 10:19:20 +1100; Vlad Apostolov wrote: Timothy Shimmin wrote: Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directo; /archives/xfs/2007-11/msg00181.html (9,620 bytes)
11. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Mon, 19 Nov 2007 14:48:38 +1100; +#define NH_BUCKETS 65536 +#define NH_HASH(ino) (nodehash + ((ino) % NH_BUCKETS)) Hashing addresses by a power of two often results in an uneven distribution over the hashtable. Have you verified you; /archives/xfs/2007-11/msg00183.html (17,466 bytes)
12. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Mon, 19 Nov 2007 12:39:18 +0000; What parent pointers?; /archives/xfs/2007-11/msg00184.html (8,968 bytes)
13. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Mon, 19 Nov 2007 09:52:45 -0600; The ones not yet released I guess :) -Eric; /archives/xfs/2007-11/msg00185.html (9,480 bytes)
14. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Tue, 20 Nov 2007 09:08:12 +1100; Eric Sandeen wrote: Christoph Hellwig wrote: On Fri, Nov 16, 2007 at 05:20:28PM +1100, Timothy Shimmin wrote: Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to f; /archives/xfs/2007-11/msg00187.html (10,631 bytes)
15. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Tue, 20 Nov 2007 12:36:51 +1100; Something like the attached patch? This is proof-of-concept. I've compiled it but I haven't tested it. Your mission, Barry, should you choose to accept it, it to make it work ;) Cheers, Dave. -- Dave; /archives/xfs/2007-11/msg00189.html (25,353 bytes)
16. Re: REVIEW: xfs_reno #2 (score: 1): Author:; Date: Fri, 23 Nov 2007 15:30:52 +0100; David Chinner schrieb: On Thu, Oct 04, 2007 at 02:25:16PM +1000, Barry Naujok wrote: A couple changes from the first xfs_reno: - Major one is that symlinks are now supported, but only owner, group an; /archives/xfs/2007-11/msg00246.html (52,560 bytes)
17. Re: REVIEW: xfs_reno #2 (score: 1): Author: >; Date: Fri, 16 Nov 2007 17:04:09 +1100; Barry Naujok wrote: A couple changes from the first xfs_reno: - Major one is that symlinks are now supported, but only owner, group and extended attributes are copied for them (not times or inode att; /archives/xfs/2007-11/msg00483.html (10,245 bytes)
18. Re: REVIEW: xfs_reno #2 (score: 1): Author: >; Date: Fri, 16 Nov 2007 17:20:28 +1100; Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directory. This may not be that easy though. Really?; /archives/xfs/2007-11/msg00485.html (8,851 bytes)
19. Re: REVIEW: xfs_reno #2 (score: 1): Author: >; Date: Mon, 19 Nov 2007 10:13:43 +1100; Timothy Shimmin wrote: Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directory. This may not be th; /archives/xfs/2007-11/msg00496.html (9,247 bytes)
20. Re: REVIEW: xfs_reno #2 (score: 1): Author: >; Date: Mon, 19 Nov 2007 10:19:20 +1100; Vlad Apostolov wrote: Timothy Shimmin wrote: Vlad Apostolov wrote: When the XFS parent pointers feature is released we would need to find out to update the EA to point to the new inode parent directo; /archives/xfs/2007-11/msg00497.html (9,620 bytes)

Current List: 1 - 20
Page: [1] [2]