From: Scott Garman <scott.a.garman@intel.com>
To: poky@yoctoproject.org
Subject: Re: Strange ext filesystem error
Date: Wed, 26 Oct 2011 10:25:35 -0700 [thread overview]
Message-ID: <4EA8428F.9070205@intel.com> (raw)
In-Reply-To: <4EA83C08.5010002@mlbassoc.com>
On 10/26/2011 09:57 AM, Gary Thomas wrote:
> On 2011-10-26 10:44, McClintock Matthew-B29882 wrote:
>> On Wed, Oct 26, 2011 at 9:25 AM, Gary Thomas<gary@mlbassoc.com> wrote:
>>> I've noticed this behaviour on my Poky/Yocto based systems.
>>> First, I format some device, in this case an MMC card, as ext3
>>> (yes, my kernel supports ext3)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>>> # mkfs.ext3 /dev/mmcblk0p1
>>> Then, when I go to mount it, I get this error:
>>> # mount /dev/mmcblk0p1 /tmp/disk
>>> EXT2-fs (mmcblk0p1): warning: mounting ext3 filesystem as ext2
>>>
>>> Any ideas why? How can I get ext3 file system working?
>>
>> Does your kernel support ext3? Otherwise you can try:
>
> See above :-)
>
>>
>> $ mount -t ext3 /dev/mmcblk0p1 /tmp/disk
>
> This does work although forcing the file system type should not
> be necessary, but I'll live with it. This warning/error must have
> something to do with the mount program (part of busybox).
Does dmesg complain about the filesystem at all?
FWIW if the datestamps on the filesystem are unusual (e.g, in the
future), this would likely cause problems when mouting them. But
generally I would think that might raise a warning to run fsck, and not
cause an ext3 fs to be degraded to ext2.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-10-26 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 14:25 Strange ext filesystem error Gary Thomas
[not found] ` <CAEsOVNejiifxREadD5-Lh6_MazhH1Qh1dgWg-nAw_e1yA8kTXA@mail.gmail.com>
2011-10-26 16:57 ` Gary Thomas
2011-10-26 17:25 ` Scott Garman [this message]
2011-10-27 0:22 ` Tom Rini
2011-10-27 7:05 ` Anders Darander
2011-10-28 10:26 ` Gary Thomas
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=4EA8428F.9070205@intel.com \
--to=scott.a.garman@intel.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.