From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: handling unrecognised mount options Date: Sun, 16 Mar 2003 03:00:03 -0800 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20030316030003.21f2942b.akpm@digeo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from digeo-nav01.digeo.com (digeo-nav01 [192.168.1.233]) by packet.digeo.com (8.12.8/8.12.8) with SMTP id h2GB05Pu009975 for ; Sun, 16 Mar 2003 03:00:05 -0800 (PST) To: linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net List-Id: linux-fsdevel.vger.kernel.org None of my machines will successfully boot into 2.4 kernels because I have "commit=30" added to the ext3 mount options in /etc/fstab. The ext3 driver in those kernels does not to recognise that option and it fails the mount. This seems to be a fairly gratuitous and pointless forward-incompatibility. I propose that henceforth filesystems will, when presented with an unrecognised mount option, warn and proceed with the mount anyway. Can anyone see any problems with that?