[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48E0E7D4.1090409@sandeen.net>
Date: Mon, 29 Sep 2008 09:36:04 -0500
From: Eric Sandeen <sandeen@...deen.net>
To: Christoph Hellwig <hch@...radead.org>
CC: Takashi Sato <t-sato@...jp.nec.com>,
Ric Wheeler <rwheeler@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Oleg Nesterov <oleg@...sign.ru>, linux-fsdevel@...r.kernel.org,
dm-devel@...hat.com, viro@...IV.linux.org.uk,
linux-ext4@...r.kernel.org, xfs@....sgi.com, axboe@...nel.dk,
mtk.manpages@...glemail.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] Add timeout feature
Christoph Hellwig wrote:
> On Fri, Sep 26, 2008 at 05:52:35PM +0900, Takashi Sato wrote:
>> I think that your concern is that the freezer cannot recognize the occurrence
>> of a timeout and it continues the backup process and the backup data is
>> corrupted finally.
>
> What timeout should happen? the freeze ioctl must not return until the
> filesystem is a clean state and all writes are blocked.
The suggestion was that *UN*freeze would return ETIMEDOUT if the
filesystem had already unfrozen itself, I think. That way you know that
the snapshot you just took is worthless, at least.
I'm still not really sold on the timeout, but I think the above was the
intent.
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists