xfs
[Top] [All Lists]

Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inode

To: Damien Wyart <damien.wyart@xxxxxxxxx>
Subject: Re: [PATCH block/for-linus] writeback: fix syncing of I_DIRTY_TIME inodes
From: Tejun Heo <tj@xxxxxxxxxx>
Date: Mon, 17 Aug 2015 16:00:34 -0400
Cc: Jan Kara <jack@xxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, Eryu Guan <eguan@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, axboe@xxxxxx, Jan Kara <jack@xxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, kernel-team@xxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=F6l/kwZQK6sReY4XkmCPDygnqFDcg5URs7KbFCgD2rU=; b=XEVfUrXI9AYA8qa+THH5+gDjXNjwB6K5LhXHPDOFxMVk+7YBDIhRM+ltiSXN/eOjbF U3Swpq3nd/RZmIcUqx+pknmvzuId7i9Dxg8Kx5IS577MS2RJeneQOcHZCZ6HN1SnE5xZ FyHqgHU1zQr5pzn7XR3pgVEdCr8EsuPo5HmrhOpthZZNKpYMijMzjtLZ9us28tWHYfV9 leEQcExTiaGO0uBAb/Pqvqfg2mubeOpZl4jM1G1UbPsJcveDJhcNvaKFysoo7TxmFRcB 5Xq8+HvPEvZW1a7SZUMAWfs4HpX5icAbtAF5LOUPa2RDQMv2xKhv6rW2tud1BZznj5Nv r7AQ==
In-reply-to: <20150814151401.GA6906@brouette>
References: <20150812101204.GE17933@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20150813004435.GN3902@dastard> <20150813224415.GG4496@xxxxxxxxxxxxxxx> <20150814111408.GB8710@xxxxxxxxxxxxx> <20150814151401.GA6906@brouette>
Sender: Tejun Heo <htejun@xxxxxxxxx>
User-agent: Mutt/1.5.23 (2014-03-12)
Hello, Damien.

On Fri, Aug 14, 2015 at 05:14:01PM +0200, Damien Wyart wrote:
> I had an unstable system when running latest Linus tree with Tejun's
> patch applied on top. Nothing fishy in the logs after rebooting without
> the patch, but remote access with ssh when patch applied did not work
> (as if /home partition could not be read). This system has / as ext4 and
> other partitions (including /home) as XFS. Trying to login on tty
> instead of X resulted in hang of X. I could reboot with sysrq, but can't
> do further tests at the moment.
> 
> Back to same tree without the patch resulted in normal system.
> 
> So just a heads up the patch doesn't seem OK in its current state.

Have you been able to reproduce the failure?  That sounds like an
unlikely failure mode for the patch.

Thanks.

-- 
tejun

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