On Sat, Jan 8, 2011 at 5:20 PM, Ken Moffat <k...@linuxfromscratch.org> wrote:
> On Sat, Jan 08, 2011 at 07:24:09PM +0000, Ken Moffat wrote:
>>  _if_ you have made a filesystem as ext4, that nasty looking 'error'
>> is actually normal.  I think it is normally followed (in my case) by
>> a similar message about ext3, before successfully mounting it as
>> ext4.  Unfortunately, these error messages do not get logged so I
>> can't look back to see exactly what was reported in my case.
>>
>  Correction (now that I've just booted a fresh build, I had a chance
> to examine the messages) - in my case, one message per filesystem
> (/boot, /home), text exactly as you quoted, even though my /boot is
> supposed to be ext2.  And, I didn't actually notice any reports that
> these filesystems had indeed mounted.  If I got a similar message
> from my root fs, it had scrolled off the screen before I saw it.
>
>  So, that part of your output is normal.
>
>  I'm wondering if you have no console on which to see the later
> output.  If you mount your new system at /mnt/lfs from the host,
> and *do not* bind the host's /dev, does /mnt/lfs/dev contain
> console (char special device 5 1) and
> null (char special device 1 3) ?
>
> ĸen
> --
> das eine Mal als Tragödie, das andere Mal als Farce
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>

There's now a kernel option to mount ext2/ext3 as ext4.  If you
compile that option in, you'll get that error on ext2/ext3
filesystems.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to