Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754720AbcKUPj5 convert rfc822-to-8bit (ORCPT ); Mon, 21 Nov 2016 10:39:57 -0500 Received: from dresden.studentenwerk.mhn.de ([141.84.225.229]:33334 "EHLO email.studentenwerk.mhn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753882AbcKUPjz (ORCPT ); Mon, 21 Nov 2016 10:39:55 -0500 From: Wolfgang Walter To: LKML Cc: linux-ext4@vger.kernel.org Subject: external journal an data= option Date: Mon, 21 Nov 2016 16:39:53 +0100 Message-ID: <5330915.k0A4yo7VY8@stwm.de> User-Agent: KMail/4.14.3 (Linux/4.4.0-45-generic; KDE/4.14.13; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 746 Lines: 27 Hello, while testing ext4 with an external journal I found the following problem with longterm kernel 4.4.30: I could mount the filesystem without specifying the option data=.... It seems that it is then mounted with data=ordered and indeed this is what cat /proc/mounts shows. But I could not change any option afterwards with -o remount. It always said that data=ordered is not valid with an external journal. If I mount with explicitly stating data=writeback or data=journal remount works fine. So It seems that ext4 does forbid (at least in 4.4.30) data=ordered as an option but uses it implicitly as default mode even with an external journal. Regards, -- Wolfgang Walter Studentenwerk M?nchen Anstalt des ?ffentlichen Rechts