[Top] [All Lists]

Re: Delaylog information enquiry

To: "Frank ." <frank_1005@xxxxxxx>
Subject: Re: Delaylog information enquiry
From: Brian Foster <bfoster@xxxxxxxxxx>
Date: Tue, 29 Jul 2014 08:38:16 -0400
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <DUB129-W7B2973281D7E749989D43EEF80@xxxxxxx>
References: <DUB129-W7B2973281D7E749989D43EEF80@xxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
On Tue, Jul 29, 2014 at 10:53:09AM +0200, Frank . wrote:
> Hello. 
> I just wanted to have more information about the delaylog feature. 
> From what I understood it seems to be a common feature from different FS. 
> It's supposed to retain information such as metadata for a time ( how much 
> ?). Unfortunately, I could not find further information about journaling log 
> section in the XFS official documentation. 
> I just figured out that delaylog feature is now included and there is no way 
> to disable it 
> (http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/xfs.txt?id=HEAD).

There is a design document for XFS delayed logging co-located with the
xfs doc:


I'm not an expert on the delayed logging infrastructure so I can't give
details, but it's basically a change to aggregate logged items into a
list (committed item list - CIL) and "local" areas of memory (log
vectors) at transaction commit time rather than logging directly into
the log buffers. The benefits and tradeoffs of this are described in the
link above. One tradeoff is that more items can be aggregated before a
checkpoint occurs, so that naturally means more items are batched in
memory and written to the log at a time.

This in turn means that in the event of a crash, more logged items are
lost than the older, less efficient implementation. This doesn't effect
the consistency of the fs, which is the purpose of the log.

> Whatever the information it could be, I understood that this is a temporary 
> memory located in RAM. 
> Recently, I had a crash on a server and I had to execute the repair procedure 
> which worked fine. 

A crash should typically only require a log replay and that happens
automatically on the next mount. If you experience otherwise, it's a
good idea to report that to the list with the data listed here:


> But I would like to disable this feature to prevent any temporary data not to 
> be written do disk. (Write cache is already disabled on both hard drive and 
> raid controller). 
> Perhaps it's a bad idea disabling it. If so, I would like to have your 
> opinion about where memory corruption could happen. 

Delayed logging is not configurable these days. The original
implementation was optional via a mount option, but my understanding is
that might have been more of a precaution for a new feature than a real
tuning option.

If you want to ensure consistency of certain operations, those
applications should issue fsync() calls as appropriate. You could also
look into the 'wsync' mount option (and probably expect a significant
performance hit).


> Any help would be much appreciated. 
> Thank you. 

> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

<Prev in Thread] Current Thread [Next in Thread>