From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] EXT2-fs error
Date: Mon, 13 Sep 2010 11:22:31 +0200 [thread overview]
Message-ID: <87mxrm6lrc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <SNT119-W9D3C2902126B58DEE9A1282770@phx.gbl> (Johnny Beardsmore's message of "Mon, 13 Sep 2010 08:45:56 +0000")
>>>>> "Johnny" == Johnny Beardsmore <jny0@hotmail.com> writes:
Johnny> My understanding of running e2fsck is that it should only be
Johnny> done on an unmounted file system (or setting to read-only, but
Johnny> I've never actually done this). I've only ever run it on hda
Johnny> (usually a hard disk or flash drive) or sda (usually a usb
Johnny> stick) after a umount. For me to e2fsck on the build machine
Johnny> means that I'm applying it to files on a mounted file system,
Johnny> not a complete unmounted drive. This is where I'm getting
Johnny> confused.
Here it works:
tar jxf buildroot-2010.08.tar.bz2
cd buildroot-2010.08
make menuconfig (don't change anything, exit and save)
make
/sbin/e2fsck -f output/images/rootfs.ext2
e2fsck 1.41.9 (22-Aug-2009)
Filesystem did not have a UUID; generating one.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
output/images/rootfs.ext2: ***** FILE SYSTEM WAS MODIFIED *****
output/images/rootfs.ext2: 504/896 files (0.4% non-contiguous), 1268/3568 blocks
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-13 9:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 9:35 [Buildroot] EXT2-fs error JNY
2010-09-01 9:53 ` Peter Korsgaard
2010-09-02 11:17 ` JNY
2010-09-03 5:56 ` Mitch Davis
2010-09-03 5:57 ` Mitch Davis
2010-09-07 16:58 ` JNY
2010-09-07 23:57 ` Mitch Davis
2010-09-08 8:31 ` JNY
2010-09-09 12:35 ` Johnny Beardsmore
2010-09-10 15:41 ` Johnny Beardsmore
2010-09-10 16:12 ` Johnny Beardsmore
2010-09-10 16:16 ` Yann E. MORIN
2010-09-13 7:51 ` Johnny Beardsmore
2010-09-13 8:20 ` Thomas Petazzoni
2010-09-13 8:45 ` Johnny Beardsmore
2010-09-13 9:22 ` Peter Korsgaard [this message]
2010-09-15 11:07 ` Johnny Beardsmore
2010-09-15 11:31 ` Thomas Petazzoni
2010-09-15 12:39 ` Johnny Beardsmore
2010-09-15 13:28 ` Malte Starostik
2010-09-15 17:07 ` Thomas Petazzoni
2010-09-16 6:50 ` Johnny Beardsmore
2010-09-16 7:01 ` [Buildroot] FW: " Johnny Beardsmore
2010-09-16 8:51 ` [Buildroot] " Ormund Williams
2010-09-16 9:21 ` Johnny Beardsmore
[not found] ` <AANLkTinbDS1nrt4b6TgctMwHArtwrX7_JSrzbeqxWCn=@mail.gmail.com>
2010-09-16 10:11 ` Johnny Beardsmore
2010-09-16 10:14 ` Mitch Davis
[not found] ` <233D327176C4471A9A40B36BC1B4EB35@AP366>
2010-09-16 11:14 ` Johnny Beardsmore
2010-09-16 11:57 ` Mitch Davis
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=87mxrm6lrc.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox