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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*How\s+long\s+should\s+an\s+xfs_freeze\s+take\?\s*$/: 30 ]

Total 30 documents matching your query.

1. Re: How long should an xfs_freeze take? (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: 01 Feb 2002 15:38:53 -0600; Hi Chris - Want to try this? -- /usr/tmp/TmpDir.12545-0/linux/fs/xfs/xfs_fsops.c_1.72 Fri Feb 1 15:33:39 2002 +++ linux/fs/xfs/xfs_fsops.c Fri Feb 1 15:33:51 2002 @@ -563,9 +563,6 @@ /* Flush delallo; /archives/xfs/2002-02/msg00014.html (8,568 bytes)
2. Re: How long should an xfs_freeze take? (score: 1): Author: Chris Pascoe <c.pascoe@xxxxxxxxxxxxxx>; Date: Sat, 2 Feb 2002 17:02:18 +1000; Quoting Eric Sandeen <sandeen@xxxxxxx>: Seems to speed everything up here too - after my initial rsync, the freeze takes next to no time! xfs_repair -n's on a snapshot taken just after the freeze see; /archives/xfs/2002-02/msg00037.html (9,165 bytes)
3. xfs (score: 1): Author: >; Date: 01 Feb 2002 15:38:53 -0600; /archives/xfs/2002-02/msg00588.html (8,568 bytes)
4. ice (score: 1): Author: >; Date: Sat, 2 Feb 2002 17:02:18 +1000; /archives/xfs/2002-02/msg00611.html (9,165 bytes)
5. D fails (score: 1): Author: a@xxxxxxxxxx>; Date: Tue, 29 Jan 2002 15:26:30 +1000; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg00804.html (9,875 bytes)
6. ion" (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 16:03:19 +1000; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg00863.html (10,134 bytes)
7. on xfs added to filemap.c (score: 1): Author: xxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 07:47:38 -0600; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg00865.html (9,014 bytes)
8. flush with 2.4.1[4|7]-xfs (score: 1): Author: deen@xxxxxxx>; Date: Thu, 31 Jan 2002 08:51:50 +1000; 6 hours is a long time for an unmount! The volume is ~70GB, and had no activity on it before I tried to create the snapshots - the machine had just been rebooted before some attempts. is It just see; /archives/xfs/2002-01/msg00882.html (9,386 bytes)
9. nded attributes interface (score: 1): Author: m@xxxxxxxxxx>; Date: 30 Jan 2002 17:11:49 -0600; Whoa! it was early this morning, I missed a few digits when I read the elapsed time! Yes, that is a leetle on the long side. There is a complex loop in the xfs_syncsub function, not sure yet how it c; /archives/xfs/2002-01/msg00885.html (10,433 bytes)
10. tore fails: assertion failure in do_next_mark (score: 1): Author: hans@xxxxxxx>; Date: Fri, 1 Feb 2002 08:04:32 +1000 (EST); Hi Steve, that it at I can repeat this fairly reliably now - do a meaningless rsync across the disk (i.e. rsync itself to itself - makes it stat every file on the disk, I guess), then try an xfs_free; /archives/xfs/2002-01/msg00911.html (9,095 bytes)
11. _mark (score: 1): Author: xxxxxxxxxxxx>; Date: 31 Jan 2002 16:07:07 -0600; We are looking - or at least Eric is.... Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx; /archives/xfs/2002-01/msg00912.html (10,466 bytes)
12. take? (score: 1): Author: lord@xxxxxxx>; Date: 31 Jan 2002 16:11:34 -0600; Ok, so the device you're freezing has about 60G in about 600,000 files? And freeze only takes a very long time if you've poked at each file w/ rsync first? i.e. if you unmount, then remount, xfs_free; /archives/xfs/2002-01/msg00913.html (9,156 bytes)
13. le blocking setting. (score: 1): Author: x>; Date: Tue, 29 Jan 2002 15:26:30 +1000; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg01733.html (9,875 bytes)
14. /XFS: "failed to get (valid) bulkstat information" (score: 1): Author: ns@xxxxxxxxxxxxxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 16:03:19 +1000; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg01792.html (10,134 bytes)
15. XFS footprint (was Re: TAKE - remove a function xfs added to filemap.c (score: 1): Author: ergs" <rabe@xxxxxxxxxxxxxx>; Date: Wed, 30 Jan 2002 07:47:38 -0600; I'm guessing an xfs_freeze shouldn't take this long, am I correct? real 344m40.434s user 0m0.000s sys 340m40.810s The system is a Dual CPU P3 Xeon with 1GB RAM (highmem enabled), running 2.4.17 CVS,; /archives/xfs/2002-01/msg01794.html (9,014 bytes)
16. s (score: 1): Author: c Sandeen <sandeen@xxxxxxx>; Date: Thu, 31 Jan 2002 08:51:50 +1000; 6 hours is a long time for an unmount! The volume is ~70GB, and had no activity on it before I tried to create the snapshots - the machine had just been rebooted before some attempts. is It just see; /archives/xfs/2002-01/msg01811.html (9,386 bytes)
17. ke? (score: 1): Author: Miller" <davem@xxxxxxxxxx>; Date: 30 Jan 2002 17:11:49 -0600; Whoa! it was early this morning, I missed a few digits when I read the elapsed time! Yes, that is a leetle on the long side. There is a complex loop in the xfs_syncsub function, not sure yet how it c; /archives/xfs/2002-01/msg01814.html (10,433 bytes)
18. stion (score: 1): Author: han Scott <nathans@xxxxxxx>; Date: Fri, 1 Feb 2002 08:04:32 +1000 (EST); Hi Steve, that it at I can repeat this fairly reliably now - do a meaningless rsync across the disk (i.e. rsync itself to itself - makes it stat every file on the disk, I guess), then try an xfs_free; /archives/xfs/2002-01/msg01840.html (9,095 bytes)
19. xfsrestore fails: assertion failure in do_next_mark (score: 1): Author: e <c.pascoe@xxxxxxxxxxxxxx>; Date: 31 Jan 2002 16:07:07 -0600; We are looking - or at least Eric is.... Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx; /archives/xfs/2002-01/msg01841.html (10,466 bytes)
20. o_next_mark (score: 1): Author: >; Date: 31 Jan 2002 16:11:34 -0600; Ok, so the device you're freezing has about 60G in about 600,000 files? And freeze only takes a very long time if you've poked at each file w/ rsync first? i.e. if you unmount, then remount, xfs_free; /archives/xfs/2002-01/msg01842.html (9,156 bytes)

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