[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1520005411.24467.334.camel@infinera.com>
Date: Fri, 2 Mar 2018 15:43:33 +0000
From: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
To: "lczerner@...hat.com" <lczerner@...hat.com>,
"sandeen@...hat.com" <sandeen@...hat.com>
CC: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature
incompatibilities
On Fri, 2018-03-02 at 09:34 -0600, Eric Sandeen wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>
> On 3/2/18 9:20 AM, Joakim Tjernlund wrote:
> > On Fri, 2018-03-02 at 08:42 -0600, Eric Sandeen wrote:
>
> ...
>
> > > ext3 is always going to print a message if mount fails for this reason; it
> > > has no idea that ext4 will be tried next, all it knows is that it was told
> > > to mount, and it can't.
> >
> > But I don't hav ext3, only ext4 in kernel:
> > # CONFIG_EXT2_FS is not set
> > # CONFIG_EXT3_FS is not set
> > CONFIG_EXT4_FS=y
> >
> > ext4 know's ext3 and complains as is today. In this config one should not have to see
> > this error.
>
> ext4.ko was told to mount your disk /as an ext3 filesystem/, and ext4.ko issued an
> error saying that was not possible. It is doing the right thing.
hmm, so you think there is a bug in my system ?
It works for you(no error msg) if you specify auto type in fstab?
Jocke
Powered by blists - more mailing lists