From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755265AbbIWUtA (ORCPT ); Wed, 23 Sep 2015 16:49:00 -0400 Received: from imap.thunk.org ([74.207.234.97]:39538 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755012AbbIWUs4 (ORCPT ); Wed, 23 Sep 2015 16:48:56 -0400 Date: Wed, 23 Sep 2015 16:48:46 -0400 From: "Theodore Ts'o" To: Artem Bityutskiy Cc: Chris Mason , linux-ext4@vger.kernel.org, Johannes Weiner , axboe@kernel.dk, Tejun Heo , linux-fsdevel@vger.kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org, adilger.kernel@dilger.ca, kernel-team@fb.com, "linux-kernel@vger.kernel.org" Subject: Re: [PATCH 2/2] ext4: implement cgroup writeback support Message-ID: <20150923204846.GI3318@thunk.org> Mail-Followup-To: Theodore Ts'o , Artem Bityutskiy , Chris Mason , linux-ext4@vger.kernel.org, Johannes Weiner , axboe@kernel.dk, Tejun Heo , linux-fsdevel@vger.kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org, adilger.kernel@dilger.ca, kernel-team@fb.com, "linux-kernel@vger.kernel.org" References: <1434495193-31182-1-git-send-email-tj@kernel.org> <1434495193-31182-3-git-send-email-tj@kernel.org> <20150722035620.GD2944@thunk.org> <1443012552.19983.209.camel@gmail.com> <20150923172535.GC25218@ret.masoncoding.com> <20150923175337.GD25218@ret.masoncoding.com> <20150923182432.GH3318@thunk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 23, 2015 at 10:47:16PM +0300, Artem Bityutskiy wrote: > And, by the way, I forgot this detail - I cut AC power off at the > end, then put it back on after a 20 seconds delay. I mean, this is a > clean reboot, but with power cut at the end. Is this reproducible without the power cut? And what model SSD are you using, and are you sure that it has Power Loss Protection (many SSD vendors use power loss protection as the price discrimination feature between consumer-grade SSD and enterprise-grade SSD's that cost $$$). If this problem wasn't showing up with 4.2, and is only failing with 4.3-rcX, then it might not be a hardware issue --- but it's also possible that there was a timing issue which was hiding a hardware problem. So for the purposes of debugging, removing the power cut from the set of variables is a useful thing to do. - Ted