From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6752] New: genext2fs: e2fsck must run before tunefs -U random
Date: Sun, 5 Jan 2014 21:02:27 +0000 (UTC) [thread overview]
Message-ID: <bug-6752-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6752
Summary: genext2fs: e2fsck must run before tunefs -U random
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: daniel at exxm.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5138
--> https://bugs.busybox.net/attachment.cgi?id=5138
patch
In fs/ext2/genext2fs.sh, e2fsck must run after changing filesystem options and
before setting the UUID with "tune2fs -U random". Otherwise, the latter command
will fail.
I previously got this error message
"tune2fs 1.42.9 (28-Dec-2013)
Please run e2fsck on the filesystem."
It worked for me after moving e2fsck before "tune2fs -U random"
This is based on commit bfbe4dd19e94fb24037e3b6080acd75435adbb67
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-01-05 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 21:02 bugzilla at busybox.net [this message]
2014-01-05 21:03 ` [Buildroot] [Bug 6752] genext2fs: e2fsck must run before tunefs -U random bugzilla at busybox.net
2014-01-05 22:09 ` bugzilla at busybox.net
2014-01-05 22:19 ` bugzilla at busybox.net
2014-01-05 22:30 ` bugzilla at busybox.net
2014-01-05 22:31 ` bugzilla at busybox.net
2014-01-05 22:37 ` bugzilla at busybox.net
2014-01-05 22:59 ` bugzilla at busybox.net
2014-01-05 23:20 ` bugzilla at busybox.net
2014-01-05 23:25 ` bugzilla at busybox.net
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=bug-6752-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.