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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Snapshots\s*$/: 10 ]

Total 10 documents matching your query.

1. Snapshots (score: 1): Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>; Date: Thu, 2 May 2002 12:47:06 -0400; XFS team, I've just become aware of a problem on another Journaled file-system (it is not a Linux filesystem). With this filesystem, the meta-data can be out of sync during a snapshot operation. If t; /archives/xfs/2002-05/msg00049.html (7,411 bytes)
2. Re: Snapshots (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Thu, 2 May 2002 19:07:36 +0200 (CEST); A NAS device perhaps? AFAIK XFS has a freeze/thaw operation and some others are using it together with LVM to create snapshots of filesystems. I have no idea how heavy this is used out there but we d; /archives/xfs/2002-05/msg00050.html (8,346 bytes)
3. Re: Snapshots (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 02 May 2002 12:01:51 -0500; man xfs_freeze Or if you have the correct LVM patches in place then the kernel does it all for you. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxx; /archives/xfs/2002-05/msg00051.html (8,433 bytes)
4. re[2]: Snapshots (score: 1): Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>; Date: Thu, 2 May 2002 16:14:11 -0400; Thanks for the info, and no it is a normal everyday FS. (And a mature one at that. Atleast 5 years old, but I guess hardware snapshots are relatively new. ) The problem apparently occurs in both dir; /archives/xfs/2002-05/msg00056.html (7,747 bytes)
5. RE: Snapshots (score: 1): Author: "Stephenson, Dale" <dstephenson@xxxxxxxxxxxxxx>; Date: Fri, 3 May 2002 09:31:17 -0700; [on XFS with LVM snapshots...] I've been using XFS with snapshots off-and-on for quite a while, mostly with good results (currently using XFS CVS from March 19th and LVM 1.0.3, both with some patches; /archives/xfs/2002-05/msg00062.html (11,011 bytes)
6. Re: Suggested memory size (score: 1): Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>; Date: Thu, 2 May 2002 12:47:06 -0400; ld be better, memory size should not be the issue then, more can device A and the CPU keep up with device B. I would recommend trying it out on a regular box with this amount of memory (u; /archives/xfs/2002-05/msg00687.html (7,411 bytes)
7. ted memory size (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Thu, 2 May 2002 19:07:36 +0200 (CEST); ve just become aware of a problem on another Journaled file-system (it is not a Linux filesystem). With this filesystem, the meta-data can be out of sync during a snapshot operation. If t; /archives/xfs/2002-05/msg00688.html (8,346 bytes)
8. e (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 02 May 2002 12:01:51 -0500; perhaps? AFAIK XFS has a freeze/thaw operation and some others are using it together with LVM to create snapshots of filesystems. I have no idea how heavy this is used out there but we d; /archives/xfs/2002-05/msg00689.html (8,433 bytes)
9. n (score: 1): Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>; Date: Thu, 2 May 2002 16:14:11 -0400; ve switched from his debug version of the code to the real one without a rebuild. This fixes it again. Steve The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x; /archives/xfs/2002-05/msg00694.html (7,747 bytes)
10. move m_peraglock locking) (score: 1): Author: "Stephenson, Dale" <dstephenson@xxxxxxxxxxxxxx>; Date: Fri, 3 May 2002 09:31:17 -0700; reate performance dropoff as filesystems fill up. The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:118173a linux/fs/xfs/xfs_ialloc; /archives/xfs/2002-05/msg00700.html (11,011 bytes)

Current List: 1 - 10
Page: [1]