<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
My understanding of running e2fsck is that it should only be done on an
unmounted file system (or setting to read-only, but I've never actually
done this). I've only ever run it on hda (usually a hard disk or flash
drive) or sda (usually a usb stick) after a umount. For me to e2fsck
on the build machine means that I'm applying it to files on a mounted
file system, not a complete unmounted drive. This is where I'm getting
confused.<br>
<br>
I'm obviously lacking some fundermental understanding of what e2fsck
does. I know to run it when advised to after repartitionning (entire)
drives with fdisk, and if I don't then sooner or later, inode errors
start popping up, and data gets lost. I'm getting the advisory on
start-up and as I'd expect, I'm getting inode errors on occasion. What
I can't seem to do is use the fix I'd normally apply.<br><br>> Date: Mon, 13 Sep 2010 10:20:31 +0200<br>> From: thomas.petazzoni@free-electrons.com<br>> To: buildroot@busybox.net<br>> Subject: Re: [Buildroot] EXT2-fs error<br>> <br>> Hello,<br>> <br>> On Mon, 13 Sep 2010 07:51:55 +0000<br>> Johnny Beardsmore <jny0@hotmail.com> wrote:<br>> <br>> > 1) e2fsck the rootfs file on the build machine. This creates an error thus:<br>> <br>> Yann Morin has already told you that you are trying to run e2fsck on a<br>> tarball. A tarball is not an ext2 image, so obviously it cannot work.<br>> <br>> What you're doing is exactly as if your trying to run an image<br>> verification program on a text document. It doesn't work because it<br>> makes no sense to try it in the first place.<br>> <br>> Regards,<br>> <br>> Thomas<br>> -- <br>> Thomas Petazzoni, Free Electrons<br>> Kernel, drivers, real-time and embedded Linux<br>> development, consulting, training and support.<br>> http://free-electrons.com<br>> _______________________________________________<br>> buildroot mailing list<br>> buildroot@busybox.net<br>> http://lists.busybox.net/mailman/listinfo/buildroot<br>                                            </body>
</html>