From: Philippe Leduc <ledphilippe@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: mount fat regression
Date: Thu, 25 Feb 2016 10:42:42 +0100 [thread overview]
Message-ID: <CABQt-UkPF+RqCp7n1W-QzRXvpk4aSjjEpSVVGe2oSYkt-gVf5A@mail.gmail.com> (raw)
In-Reply-To: <CABQt-Unp1Kacvc5jwUcwstatUtm6VQ0ROr2CHcQVtL85YizkmA@mail.gmail.com>
I loaded our 'old' barebox (barebox 2015.10.0-01455-g90387ba) and here
is the output of filetype (same board):
filetype /dev/mmc2.netcom
/dev/mmc2.netcom: FAT filesytem (fat)
Philippe LEDUC
ledphilippe@gmail.com
2016-02-25 10:37 GMT+01:00 Philippe Leduc <ledphilippe@gmail.com>:
> Hi,
>
> This was working before :) (at least with barebox version 2015.10).
> Honestly , this may be a misconfiguration on our part (and the fact
> that it worked doesn't mean that it was a normal behavior).
>
> Here is the output:
> filetype /dev/mmc2.netcom
> /dev/mmc2.netcom: MBR sector (mbr)
>
> And it is cleary different with a working partition:
> filetype /dev/mmc1.0
> /dev/mmc1.0: FAT filesytem (fat)
>
> I format the partitions with fatfs f_mkfs, and I do not use f_disk to
> create partition table. This could be the problem. I'll check that
> point.
>
> Best regards,
>
> --
> Philippe LEDUC
> ledphilippe@gmail.com
>
>
> 2016-02-25 9:56 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
>> On Wed, Feb 24, 2016 at 05:44:42PM +0100, Philippe Leduc wrote:
>>> Hi,
>>>
>>> It seems that there is a regression in the mount command for fat
>>> filesystem: if I try to mount a partition that is formatted with
>>> fatfs, I got this error:
>>>
>>> mount /dev/mmc2.netcom
>>> mount: No such file or directory
>>>
>>> I do not have the problem with a fat formatted with Windows or Linux.
>>>
>>> Do you have an idea?
>>
>> Are you sure this is a regression? Did this work before? I don't think
>> that FAT support in general is broken, it's probably something with your
>> special setup.
>>
>> What does 'filetype /dev/mmc2.netcom' give you?
>>
>> Sascha
>>
>> --
>> Pengutronix e.K. | |
>> Industrial Linux Solutions | http://www.pengutronix.de/ |
>> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-25 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 16:44 Philippe Leduc
2016-02-25 8:56 ` Sascha Hauer
2016-02-25 9:37 ` Philippe Leduc
2016-02-25 9:42 ` Philippe Leduc [this message]
2016-02-25 9:51 ` Sascha Hauer
2016-02-25 10:23 ` Philippe Leduc
2016-02-25 10:52 ` Philippe Leduc
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=CABQt-UkPF+RqCp7n1W-QzRXvpk4aSjjEpSVVGe2oSYkt-gVf5A@mail.gmail.com \
--to=ledphilippe@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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