From: Alun <alun.linux@ty-penguin.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: kzak@redhat.com, util-linux@vger.kernel.org
Subject: Re: [PATCH] Add option to fsfreeze to call syncfs() prior to freezing.
Date: Sat, 8 Dec 2012 19:46:41 +0000 [thread overview]
Message-ID: <20121208194641.3efe5087@aspire.ty-penguin.org.uk> (raw)
In-Reply-To: <20121208124743.GA18956@infradead.org>
On Sat, 8 Dec 2012 07:47:43 -0500
Christoph Hellwig <hch@infradead.org> wrote:
> On Fri, Dec 07, 2012 at 12:50:32PM +0000, Alun wrote:
> > Christoph Hellwig <hch@infradead.org> said, in message
> > 20121207124415.GA28504@infradead.org:
> > >
> > > It might be better to send a kernel patch to do a first async sync
> > > attempt instead of band aiding this in one of the consumers.
> >
> > That's what I did originally - see
> > http://marc.info/?t=135474654500003&r=1&w=2
>
> So let's keep the discussion there, if you do exactly the same call
> from userspace the same arguments still apply.
I'm out of my depth when it comes to the politics of all this. So I
think I'm going to bow out now. I'd already got the solution to my
specific issue (write a tiny "syncfs" program and call it from my
script prior to taking a snapshot). While I'd like to try and help
others avoid the same pitfall as me, I'm not motivated enough to
blunder any further into this disagreement.
Cheers,
Alun.
next prev parent reply other threads:[~2012-12-08 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 10:14 [PATCH] Add option to fsfreeze to call syncfs() prior to freezing Alun
2012-12-07 11:17 ` Alun
2012-12-07 12:44 ` Christoph Hellwig
2012-12-07 12:50 ` Alun
2012-12-08 12:47 ` Christoph Hellwig
2012-12-08 19:46 ` Alun [this message]
2013-03-20 13:28 ` Karel Zak
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=20121208194641.3efe5087@aspire.ty-penguin.org.uk \
--to=alun.linux@ty-penguin.org.uk \
--cc=hch@infradead.org \
--cc=kzak@redhat.com \
--cc=util-linux@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