[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180306131110.4r2rent47qf3awmk@rh_laptop>
Date: Tue, 6 Mar 2018 14:11:10 +0100
From: Lukas Czerner <lczerner@...hat.com>
To: Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc: "tytso@....edu" <tytso@....edu>,
"sandeen@...hat.com" <sandeen@...hat.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
kzak@...hat.com
Subject: Re: EXT4-fs (mmcblk0p1): couldn't mount as ext3 due to feature
incompatibilities
On Tue, Mar 06, 2018 at 06:23:39AM +0000, Joakim Tjernlund wrote:
> On Mon, 2018-03-05 at 22:56 -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 11:11 AM, Joakim Tjernlund wrote:
> > > On Fri, 2018-03-02 at 11:29 -0500, Theodore Ts'o wrote:
> >
> > ...
> >
> > > > So I'm not seeing this behavior at all. I created an ext4 file system
> > > > on /dev/cwcc/scratch, and then ran:
> > > >
> > > > # mount -t auto /dev/cwcc/scratch /mnt
> > >
> > > Seems like it only hits when mounting from fstab, I have
> > >
> > > LABEL=BOOT /boot auto noatime 1 2
> > >
> > > Anyhow, Eric's patch solved the problem.
> >
> > BTW which distro was this happening on?
>
> This is on Gentoo
>
> Jocke
It's good that Eric's patch fixes the complainig, however the question
is why is it trying the other fs when you have specified auto and blkid
is able to recognize it. Weird.
Do you know how the mount is called from your init script ?
Can you reproduce it by running mount -a (probably using a different
file system since it's /boot we're talking about here).
If so then please can you use these debug environment variables and show
us the output ?
LIBMOUNT_DEBUG=all LIBBLKID_DEBUG=all mount -a
Adding kzak to the cc
Thanks!
-Lukas
Powered by blists - more mailing lists