- 1. Gaurenteed file write?? (score: 1)
- Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Oct 2002 14:03:21 -0400
- _write is missing, one patch is probably missing, I will fix it in a few days, the last usable xfs was probably in 2.4.20pre5aa1. Andrea
- /archives/xfs/2002-10/msg00303.html (7,579 bytes)
- 2. Re: Gaurenteed file write?? (score: 1)
- Author: Steve Lord <lord@xxxxxxx>
- Date: 15 Oct 2002 13:45:13 -0500
- TERATION > /backup/iteration Recently this file was reset to 0. I suspect it was a case of the "zero filled file". For this specific fil
- /archives/xfs/2002-10/msg00305.html (8,513 bytes)
- 3. Re: Gaurenteed file write?? (score: 1)
- Author: "Wendy Cheng" <s_wendy_cheng@xxxxxxxxxxx>
- Date: Tue, 15 Oct 2002 15:03:14 -0400
- e marcelo merged a part of it.. Still required part of 00_o_direct-read-overflow-write-locking-xfs-1 below: diff -urNp 2.4.19rc1/include/linux/fs
- /archives/xfs/2002-10/msg00306.html (9,094 bytes)
- 4. Re: Gaurenteed file write?? (score: 1)
- Author: Steve Lord <lord@xxxxxxx>
- Date: 15 Oct 2002 14:04:35 -0500
- ync on it. sync should do it too. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx
- /archives/xfs/2002-10/msg00307.html (10,392 bytes)
- 5. Re: Gaurenteed file write?? (score: 1)
- Author: >
- Date: 17 Oct 2002 16:29:40 -0700
- onal Comments From sandeen@xxxxxxx 2002-10-17 13:33 -- More info from Luben: Here's is our setup -- more detailed: 2.4.19 stock, ftp://oss.sgi
- /archives/xfs/2002-10/msg00396.html (8,263 bytes)
- 6. Re: Gaurenteed file write?? (score: 1)
- Author: >
- Date: Fri, 18 Oct 2002 08:10:55 -0500
- ng if there were any issues that would prevent Ted's ext ACLs from co-existing with XFS's ACLs. My base kernel is 2.5.43 checked out from the
- /archives/xfs/2002-10/msg00399.html (8,672 bytes)
- 7. re[2]: Gaurenteed file write?? (score: 1)
- Author: >
- Date: Fri, 18 Oct 2002 10:01:16 -0400
- ht give you better results. -- Nate Straz
- /archives/xfs/2002-10/msg00402.html (8,032 bytes)
- 8. 1.2a1] acl problems (was: root xfs filesystem executable bits bug comeback?) (score: 1)
- Author: mm@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Oct 2002 14:03:21 -0400
- size of the page->index field, metadata is cached in an address space, so the size of a filesystem is governed by the amount of space which can fit in one of
- /archives/xfs/2002-10/msg01082.html (7,579 bytes)
- 9. k?) (score: 1)
- Author: wig <hch@xxxxxxxxxxxxx>
- Date: 15 Oct 2002 13:45:13 -0500
- re of all the problems... I am not an acl-guru by -any- means though, so I'd appreciate any testing & sanity-checking. I'll ask the sgi acl-gurus to look at it
- /archives/xfs/2002-10/msg01084.html (8,513 bytes)
- 10. resolved symbol in xfs.o (score: 1)
- Author: eve Lord <lord@xxxxxxx>
- Date: Tue, 15 Oct 2002 15:03:14 -0400
- g, one patch is probably missing, I will fix it in a few days, the last usable xfs was probably in 2.4.20pre5aa1. Andrea
- /archives/xfs/2002-10/msg01085.html (9,094 bytes)
- 11. [2.4.18-14SGI_XFS_1.2a1] acl problems (score: 1)
- Author: endy_cheng@xxxxxxxxxxx>
- Date: 15 Oct 2002 14:04:35 -0500
- ly the permissions bit seem to be fine now, but also the ghost-acl entries are gone. Definitely makes me happy! ;) Thank
- /archives/xfs/2002-10/msg01086.html (10,392 bytes)
- 12. ing special I need to do? (score: 1)
- Author: eith Owens <kaos@xxxxxxx>
- Date: 17 Oct 2002 16:29:40 -0700
- st this a bit, it would be much appreciated. Avoid creating attrs for acls which can be stored in the standard permission bits, and remove existing attrs if a
- /archives/xfs/2002-10/msg01175.html (8,263 bytes)
- 13. ck_page()) (score: 1)
- Author: n Scott <nathans@xxxxxxx>
- Date: Fri, 18 Oct 2002 08:10:55 -0500
- n@xxxxxxx 2002-10-17 13:33 -- More info from Luben: Here's is our setup -- more detailed: 2.4.19 stock, ftp://oss.sgi
- /archives/xfs/2002-10/msg01178.html (8,672 bytes)
- 14. e: XFS ACLs + Ted's EXT2/EXT3 ACLs in 2.5.43? (score: 1)
- Author: ephen Lord <lord@xxxxxxx>
- Date: Fri, 18 Oct 2002 10:01:16 -0400
- machines with la
- /archives/xfs/2002-10/msg01181.html (8,032 bytes)
- 15. Gaurenteed file write?? (score: 1)
- Author: Greg Freemyer <freemyer@xxxxxxxxxxxxxxxxx>
- Date: Tue, 15 Oct 2002 14:03:21 -0400
- All, I have an iteration counter that I update every night. echo $ITERATION > /backup/iteration Recently this file was reset to 0. I suspect it was a case of the "zero filled file". For this specific
- /archives/xfs/2002-10/msg01861.html (7,579 bytes)
- 16. Re: Gaurenteed file write?? (score: 1)
- Author: Steve Lord <lord@xxxxxxx>
- Date: 15 Oct 2002 13:45:13 -0500
- Write a little program which opens a file and calls fsync on it. sync should do it too. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx
- /archives/xfs/2002-10/msg01863.html (8,679 bytes)
- 17. Re: Gaurenteed file write?? (score: 1)
- Author: "Wendy Cheng" <s_wendy_cheng@xxxxxxxxxxx>
- Date: Tue, 15 Oct 2002 15:03:14 -0400
- Along the same line, if I mount the file system synchronously (forget about performance for now), will any write gets gaurenteed to get flushed into the disk ? More specifically, if I do step 1: moun
- /archives/xfs/2002-10/msg01864.html (9,209 bytes)
- 18. Re: Gaurenteed file write?? (score: 1)
- Author: Steve Lord <lord@xxxxxxx>
- Date: 15 Oct 2002 14:04:35 -0500
- Use wsync and sync mount options. That should do it. Probably sync on its own is enough. wsync makes xfs transactions synchronous, but the sync will make file writes synchronous and that flushes the
- /archives/xfs/2002-10/msg01865.html (10,577 bytes)
- 19. Re: Gaurenteed file write?? (score: 1)
- Author: Florin Andrei <florin@xxxxxxx>
- Date: 17 Oct 2002 16:29:40 -0700
- I always add sync at the end of critical scripts. Sometimes i insert supplemental "sync"s inside the script, after important steps are completed. But be aware that, on extremely busy machines with la
- /archives/xfs/2002-10/msg01954.html (8,429 bytes)
- 20. Re: Gaurenteed file write?? (score: 1)
- Author: Nathan Straz <nstraz@xxxxxxx>
- Date: Fri, 18 Oct 2002 08:10:55 -0500
- You might want to think about storing $ITERNATION as part of a file name instead of in a file. That way $ITERATION is part of a journal transaction. That might give you better results. -- Nate Straz
- /archives/xfs/2002-10/msg01957.html (8,868 bytes)
This search system is powered by
Namazu