mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Barebox and ext4 ? problems
Date: Wed, 16 Aug 2017 10:31:55 +0200	[thread overview]
Message-ID: <1502872315.19806.0.camel@pengutronix.de> (raw)
In-Reply-To: <87valnrk6z.fsf@gmail.com>

Hi Holger,

Am Mittwoch, den 16.08.2017, 10:27 +0200 schrieb Holger Schurig:
> Simon Aittamaa <simon.aittamaa@gmail.com> writes:
> 
> > I think it was metadata_csum and 64bit...
> 
> You're right.
> 
> My SDCard was formatted months ago, I only used rsync for the updates.
> But the eMMC was formatted afresh by a script from me. I found out with
> the feature command "debugfs" that the partitions have different
> features enables. In my case it was only 64bit, not metadata_csum.
> 
> I now use
> 
> 	mkfs.ext4 -O ^64bit -F -j -L $label /dev/mmcblk0p$partition
> 
> to format it. It spits out some ugly warning that 64bit is the best
> thing since sliced bread, but if you ignore this, then everything is
> fine!
> 
> To get rid of this uglyness, I use:
> 
> 	mkfs.ext4 -O ^64bit -F -j -L $label /dev/mmcblk0p$partition | \
> 		grep -v 64-bit | \
> 		grep -v 64bit
> 
> I think I'll post a patch to Barebox that either allows it to mount
> partions with the 64bit feature. Or to refuse the mount with a proper
> error message.

That would be much appreciated.

Regards,
Lucas


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

      reply	other threads:[~2017-08-16  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 16:31 Holger Schurig
2017-08-14 17:36 ` Ian Abbott
2017-08-16  6:15 ` Simon Aittamaa
2017-08-16  8:27   ` Holger Schurig
2017-08-16  8:31     ` Lucas Stach [this message]

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=1502872315.19806.0.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=holgerschurig@gmail.com \
    /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