| To: | Austin Gonyou <austin@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Corrupted files on 2.4.18. |
| From: | Juri Haberland <juri@xxxxxxxxxxxxxx> |
| Date: | Wed, 20 Mar 2002 19:58:05 +0100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| Organization: | totally unorganized |
| References: | <3C98D5CA.6040502@xxxxxxxxxxxxxx> <1016649759.18768.8.camel@UberGeek> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9+) Gecko/20020305 |
Austin Gonyou wrote: > does anyone know how much speed is lost by osync? I don't have any numbers but it *feels* not much slower than without -osync. Actually I'm impressed how fast this system still is (it's a workgroups server for ~10 people accessing it mostly via NFS and it runs a small news server). > On Wed, 2002-03-20 at 12:32, Juri Haberland wrote: >> Daniel Fonseca wrote: >> > I seem to remember this being a bug reported some time ago, and >> thought >> > it was corrected, though. >> >> Hmm, hmm, IMO it's not a bug, but a feature ;) If you want your data >> reliable on disk mount it -osync. Cheers, Juri |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: kmem_alloc() issues, Steve Lord |
|---|---|
| Next by Date: | TAKE - fix a bug in memory freeing, Steve Lord |
| Previous by Thread: | Re: Corrupted files on 2.4.18., Austin Gonyou |
| Next by Thread: | Re: Corrupted files on 2.4.18., Austin Gonyou |
| Indexes: | [Date] [Thread] [Top] [All Lists] |