mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* mount fat regression
@ 2016-02-24 16:44 Philippe Leduc
  2016-02-25  8:56 ` Sascha Hauer
  0 siblings, 1 reply; 7+ messages in thread
From: Philippe Leduc @ 2016-02-24 16:44 UTC (permalink / raw)
  To: barebox

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?

Best regards,

--
Philippe LEDUC
ledphilippe@gmail.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-24 16:44 mount fat regression Philippe Leduc
@ 2016-02-25  8:56 ` Sascha Hauer
  2016-02-25  9:37   ` Philippe Leduc
  0 siblings, 1 reply; 7+ messages in thread
From: Sascha Hauer @ 2016-02-25  8:56 UTC (permalink / raw)
  To: Philippe Leduc; +Cc: barebox

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-25  8:56 ` Sascha Hauer
@ 2016-02-25  9:37   ` Philippe Leduc
  2016-02-25  9:42     ` Philippe Leduc
  2016-02-25  9:51     ` Sascha Hauer
  0 siblings, 2 replies; 7+ messages in thread
From: Philippe Leduc @ 2016-02-25  9:37 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-25  9:37   ` Philippe Leduc
@ 2016-02-25  9:42     ` Philippe Leduc
  2016-02-25  9:51     ` Sascha Hauer
  1 sibling, 0 replies; 7+ messages in thread
From: Philippe Leduc @ 2016-02-25  9:42 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-25  9:37   ` Philippe Leduc
  2016-02-25  9:42     ` Philippe Leduc
@ 2016-02-25  9:51     ` Sascha Hauer
  2016-02-25 10:23       ` Philippe Leduc
  1 sibling, 1 reply; 7+ messages in thread
From: Sascha Hauer @ 2016-02-25  9:51 UTC (permalink / raw)
  To: Philippe Leduc; +Cc: barebox

On Thu, Feb 25, 2016 at 10:37:35AM +0100, Philippe Leduc wrote:
> 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)

That's your problem. With /dev/mmc2.netcom detected as MBR barebox won't
automatically try to mount a FAT filesystem.
What is /dev/mmc2.netcom anyway? I assume it's a GPT partition, right?

Can you mount the same device with the -tfat option to mount?

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-25  9:51     ` Sascha Hauer
@ 2016-02-25 10:23       ` Philippe Leduc
  2016-02-25 10:52         ` Philippe Leduc
  0 siblings, 1 reply; 7+ messages in thread
From: Philippe Leduc @ 2016-02-25 10:23 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox

> Can you mount the same device with the -tfat option to mount?
Well same problem: mount: No such file or directory

> I assume it's a GPT partition, right?
It isn't: there is no partition table, it is directly the FS on it.

> That's your problem.With /dev/mmc2.netcom detected as MBR barebox won't
automatically try to mount a FAT filesystem.
Of course it is, and if the method I am currently using to create the
FS is wrong, I'll change that, don't worry :)

Regards,

--
Philippe LEDUC
ledphilippe@gmail.com


2016-02-25 10:51 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
> On Thu, Feb 25, 2016 at 10:37:35AM +0100, Philippe Leduc wrote:
>> 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)
>
> That's your problem. With /dev/mmc2.netcom detected as MBR barebox won't
> automatically try to mount a FAT filesystem.
> What is /dev/mmc2.netcom anyway? I assume it's a GPT partition, right?
>
> Can you mount the same device with the -tfat option to mount?
>
> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: mount fat regression
  2016-02-25 10:23       ` Philippe Leduc
@ 2016-02-25 10:52         ` Philippe Leduc
  0 siblings, 0 replies; 7+ messages in thread
From: Philippe Leduc @ 2016-02-25 10:52 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: barebox

Hi again,

Thanks to you (and the filetype command), I found the root of the
problem and what happened in barebox that change the behavior.
The commit bc87f4399c6a290d820f2dd00ef772f0f3ef8767 change the
behavior of the MBR detection, and it is the right thing to do. I
discover that fatfs default behavior is to create a fdisk partition
table while I though it was a SFD one, so my addpart was wrong.

Modifiying the f_mkfs option resolve the problem.

Thank you for the help and sorry to bother you with this report.

Best regards,

--
Philippe LEDUC
ledphilippe@gmail.com


2016-02-25 11:23 GMT+01:00 Philippe Leduc <ledphilippe@gmail.com>:
>> Can you mount the same device with the -tfat option to mount?
> Well same problem: mount: No such file or directory
>
>> I assume it's a GPT partition, right?
> It isn't: there is no partition table, it is directly the FS on it.
>
>> That's your problem.With /dev/mmc2.netcom detected as MBR barebox won't
> automatically try to mount a FAT filesystem.
> Of course it is, and if the method I am currently using to create the
> FS is wrong, I'll change that, don't worry :)
>
> Regards,
>
> --
> Philippe LEDUC
> ledphilippe@gmail.com
>
>
> 2016-02-25 10:51 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
>> On Thu, Feb 25, 2016 at 10:37:35AM +0100, Philippe Leduc wrote:
>>> 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)
>>
>> That's your problem. With /dev/mmc2.netcom detected as MBR barebox won't
>> automatically try to mount a FAT filesystem.
>> What is /dev/mmc2.netcom anyway? I assume it's a GPT partition, right?
>>
>> Can you mount the same device with the -tfat option to mount?
>>
>> 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2016-02-25 10:52 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-24 16:44 mount fat regression Philippe Leduc
2016-02-25  8:56 ` Sascha Hauer
2016-02-25  9:37   ` Philippe Leduc
2016-02-25  9:42     ` Philippe Leduc
2016-02-25  9:51     ` Sascha Hauer
2016-02-25 10:23       ` Philippe Leduc
2016-02-25 10:52         ` Philippe Leduc

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox