From: Igor Gueths <igueths@attbi.com>
To: Speakup Mailing List <speakup@braille.uwo.ca>
Subject: Re: ext3 warnings
Date: Thu, 5 Dec 2002 14:33:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0212051431260.360-100000@igueths> (raw)
In-Reply-To: <20021205180707.GA1016@kc5eiv.ddts.net>
Did you get any kernel compile errors that you may not be aware of? From
here, it seems like the EXT2_FS driver is recognizing the Ext3 filesystem,
however its treating it as EXT2.
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Thu, 5 Dec 2002, William Hubbs wrote:
> Hi all,
>
> I was looking over the boot messages on this system, and I saw the
> following warnings. All of the file systems are supposed to be ext3,
> but it doesn't look like they are being treated that way.
>
> Below are the warnings I saw. Can anyone tell me what to do to get rid
> of these? Or whether I should be concerned?
>
> Thanks,
>
> William
>
> EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,9), internal journal
> EXT2-fs warning (device ide0(3,8)): ext2_read_super: mounting ext3 filesystem as ext2
>
> EXT2-fs warning (device ide0(3,7)): ext2_read_super: mounting ext3 filesystem as ext2
>
> EXT2-fs warning (device ide0(3,5)): ext2_read_super: mounting ext3 filesystem as ext2
>
> EXT2-fs warning (device ide0(3,1)): ext2_read_super: mounting ext3 filesystem as ext2
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs
` Igor Gueths [this message]
` Toby Fisher
` ext3 warnings fixed William Hubbs
` Gregory Nowak
` William Hubbs
` ext3 warnings Gregory Nowak
` Kerry Hoath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0212051431260.360-100000@igueths \
--to=igueths@attbi.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).