| To: | Takashi Sato <t-sato@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/3] Add timeout feature |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 29 Sep 2008 10:13:26 -0400 |
| Cc: | Ric Wheeler <rwheeler@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Oleg Nesterov <oleg@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, dm-devel@xxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, axboe@xxxxxxxxx, mtk.manpages@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <D0B0D91F884647D6808626CDFF81E532@nsl.ad.nec.co.jp> |
| References: | <20080908205337t-sato@mail.jp.nec.com> <20080908171119.GB22521@infradead.org> <48DBFD42.6030307@redhat.com> <D0B0D91F884647D6808626CDFF81E532@nsl.ad.nec.co.jp> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 3/3] Add timeout feature, Takashi Sato |
|---|---|
| Next by Date: | Re: REVIEW: Don't reset dirty inode flag in xfs_repair, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 3/3] Add timeout feature, Valdis . Kletnieks |
| Next by Thread: | Re: [PATCH 3/3] Add timeout feature, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |