From: Sophie Loewenthal <sophie@klunky.co.uk>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org, linux-xfs-owner@vger.kernel.org
Subject: Re: xfs delayed logging
Date: Fri, 19 May 2017 13:46:33 +0200 [thread overview]
Message-ID: <fe9fb9cc985ad9538e63eecee041583a@klunky.co.uk> (raw)
In-Reply-To: <20170519111204.GA64091@bfoster.bfoster>
Thank-you Brian.
---
http://blogs.ec.europa.eu/ECintheUK/
On 2017-05-19 13:12, Brian Foster wrote:
> On Fri, May 19, 2017 at 11:43:23AM +0200, Sophie Loewenthal wrote:
>>
>> Hi,
>>
>> Is this mount option implemented and what is the syntax?
>>
>> Reference:
>> https://www.kernel.org/doc/Documentation/filesystems/xfs-delayed-logging-design.txt
>>
>
> Delayed logging is core infrastructure and thus has been enabled by
> default for quite some time now. The associated mount options had been
> deprecated and ultimately removed in the following patch:
>
> commit 93b8a5854f247138e401471a9c3b82ccb62ff608
> Author: Christoph Hellwig <hch@infradead.org>
> Date: Tue Dec 6 21:58:07 2011 +0000
>
> xfs: remove the deprecated nodelaylog option
> ...
>
> Brian
>
>> Kind regards, Sophie
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-xfs"
>> in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-05-19 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 9:43 xfs delayed logging Sophie Loewenthal
2017-05-19 11:12 ` Brian Foster
2017-05-19 11:46 ` Sophie Loewenthal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe9fb9cc985ad9538e63eecee041583a@klunky.co.uk \
--to=sophie@klunky.co.uk \
--cc=bfoster@redhat.com \
--cc=linux-xfs-owner@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).