|
-
August 17th, 2009, 03:02 AM
#1
How to avoid log fragmentation?
Hi,
We have a project with N+1 components, each creating a log file in parallel.
On each boot the partition(NTFS) where the logs are created is checked with chkdsk /R.
These logs generate a lot of fragmentation as you can imagine, thus the chkdsk gets really slow.
What's the best method to avoid this fragmentation in your opinion?
TIA,
-
August 17th, 2009, 12:32 PM
#2
Re: How to avoid log fragmentation?
The best way would probably be to create a single, larger, log file, instead of multiple little ones.
Viggy
-
August 19th, 2009, 08:49 AM
#3
Re: How to avoid log fragmentation?
Thanks... Thought of that... but this would generate two issues:
1) logs which come from otherwise rather autonomous entities would all be entangled and would require filtering before they would be readable (this is minor issue- we can make grepping a habit )
2) we also have a Hypersonic database which writes it's data in a similar manner. And even though having just two files competing for clusters would statistically give a bit better fragmentation, the partition would still become rather fragmented over time...
-
August 23rd, 2009, 05:13 AM
#4
Re: How to avoid log fragmentation?
How about logging to a dababase? This needn't be a server-based solution - you can use SQL server compact as an embedded database.
Darwen.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|