Why is extfs filesystem mandatory?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
While trying to build a large system I keep getting an error stating that there is no room left on the device during the generation of the ext2 filesystem. It is my understanding that this is due to a hard upper limit imposed by the genext2fs utility.
This would not be an issue for me if I could simply disable said step, however there seems to be no way to disable generation of the ext2 filesystem in the menuconfig.
Is there a reason why this cannot be disabled?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMhjzbAAoJECSpOhdQESq64l8H/3+Plqt92ABJfCB+JJy93mfo PXxYko6l37BtYcbFOWFxZ8H1yvrTzXvB86Wz2ffXtAfU+n1HqOMp0Z7P7puZplJ1 ppDbXTIyu2cS+EKLIFnLoSLX6Tr0jNdoUMP2vfU6/SsSDZzmutuudMU6RrdULbPG YXUChySFxUjXfhnFZxHCUPcdbsxk9CVFZIn1CJjslSsnLDBOtdqAE5F6N/HL8IxF NeLkwk2T/wkB47e9KIDeTWc05CMMeeZKYIbqvs6LX3WecP7gYiU+vEZxIea3ezL5 pruS596+ntpM4u8n1xppzvMvPE4CLRQpgo8oVnZZaFiBjBsbVIOoiP5go++8tZ8= =8cMM
-----END PGP SIGNATURE-----
Hello,
Quoted 4 lines · On Tue, 07 Sep 2010 09:23:41 -0400 "James J. Dines" <[email protected]> wrote:
While trying to build a large system I keep getting an error stating that there is no room left on the device during the generation of the ext2 filesystem. It is my understanding that this is due to a hard upper limit imposed by the genext2fs utility.
Hum, interesting. It is not the first time we have report from people saying that fairly big filesystems cause failures while generating the ext2 image. I don't know if it's a genext2fs problem, or if it's our script that computes the number of inodes and blocks needed that does something wrong. Would be good if someone could have a look into this.
Quoted 5 lines
This would not be an issue for me if I could simply disable said step, however there seems to be no way to disable generation of the ext2 filesystem in the menuconfig.
Is there a reason why this cannot be disabled?
make menuconfig
-> Target filesystem options
-> disable 'ext2 root filesystem'
Works here. It doesn't work for you ?
Regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 5 lines · Thomas Petazzoni
Hello,
On Tue, 07 Sep 2010 09:23:41 -0400
"James J. Dines" <[email protected]> wrote:
<snip>
Quoted 11 lines
Quoted 6 lines
This would not be an issue for me if I could simply disable said step, however there seems to be no way to disable generation of the ext2 filesystem in the menuconfig.
Is there a reason why this cannot be disabled?
make menuconfig
-> Target filesystem options
-> disable 'ext2 root filesystem'
Quoted 5 lines
Works here. It doesn't work for you ?
Regards,
Thomas
In the menuconfig, under "Target Filesystems" I have an asterisk surrounded by dashes, i.e.:
- -*- ext2 root filesystem
... rather than brackets.
If I do a make defconfig I can indeed disable it, so I have attached an example config where it is disabled in case it will help track down the seeming error in a dependency somewhere.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMhmmxAAoJECSpOhdQESq65fkH/R6/rUPojzegplMfED9pdcT1 EDPkQsCnP0K3gVdXlB6qhAbh92IJJywC7jkF782LjEmQfMs/tsjYJs4uth+s02pw c3dnwjjDr/RA2FtOUdo+skfPWLpE/6/SLzILYBAv1a/0rYyh42+8Da5sJP6FsiYq OfU0/PDjKyXOGr6Rk6fnnA1Oi9vfw8Unx/eEW7h8PUd5MY4I7/oBYorqjW9R4OQq 7vuIVhqNJamAK339gP3A8xTv2ozn+p3gA+NmNovZn+m60P6VjBRuRhrkVsOXJlR2 6MeYSnLA6Bbb6scXOwQPtEf6tphCq5We+eW8N6Z3w5zpsjLaNmM/MdbD6bHKYQE=
=kH8y
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config-buildroot
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100907/23d7b156/attachment-0001.ksh>
Ar M?irt, 2010-09-07 ag 12:34 -0400, scr?obh James J. Dines:
Quoted 4 lines
In the menuconfig, under "Target Filesystems" I have an asterisk surrounded by dashes, i.e.:
- -*- ext2 root filesystem
Do you have ISO9660 FS enabled by any chance?
From the help for ext2:
Selected by: BR2_TARGET_ROOTFS_ISO9660 && (BR2_i386 || BR2_x86_64) && BR2_LINUX_KERNEL
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 5 lines · Quotient Remainder
Ar M?irt, 2010-09-07 ag 12:34 -0400, scr?obh James J. Dines:
Quoted 3 lines
In the menuconfig, under "Target Filesystems" I have an asterisk surrounded by dashes, i.e.:
Quoted 8 lines
Quoted 1 line
- -*- ext2 root filesystem
Do you have ISO9660 FS enabled by any chance?
From the help for ext2:
Selected by:BR2_TARGET_ROOTFS_ISO9660&& (BR2_i386||BR2_x86_64) &&BR2_LINUX_KERNEL
Yes, that was the issue. I have to admit I feel a bit foolish having not looked more closely at the dependencies by choosong the help option, but on the other hand I cannot imagine why this dependency exists. Obviously one can have an iso image without having an ext2 filesystem, or there would be no such thing as an iso image for Windows.
Or am I missing something?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBAgAGBQJMhnmWAAoJECSpOhdQESq67zsH/RobUwNThApVjeWikX29G9MK qyS2Kiggg8c2DV6FKeOmwBPvDgTe1QxGnGdxAPG0SgWj+GPd2mVMiha7ZaGZR+tB cEhtVBeTeDexelV8K+XLvTq3e6cLAVJ2uEuX7sc/L+P1aHlbgEdXc9MdTlUSnkic xQ4CPX5MvrXyJXimGPipb7PUjS2u6g7rDCqhsrbFeN7B/nE1vlGDcxYCEeWRoi01 ww8KtcuaGPwKw/c5bKXEED42rkQoPQWeCvZdAZauH1IEJ6K8cIKxMft+xnBDMeDJ /tdrhQLK1Q9scNqrTGEwZ/lwPrm8pL5VwxPZvPk9DH6g8eu0bvLK56V0Q7xJ6jQ= =foEH
-----END PGP SIGNATURE-----
Hello,
Quoted 6 lines · On Tue, 07 Sep 2010 13:42:47 -0400 "James J. Dines" <[email protected]> wrote:
Yes, that was the issue. I have to admit I feel a bit foolish having not looked more closely at the dependencies by choosong the help option, but on the other hand I cannot imagine why this dependency exists. Obviously one can have an iso image without having an ext2 filesystem, or there would be no such thing as an iso image for Windows.
Well, the ISO image is in fact a little bit more than just an ISO image of the filesystem: it's a bootable ISO image, and the build process for this image considers that the root filesystem is an ext2 initrd for the ISO image.
From fs/iso9660/iso9660.mk :
cp $(GRUB_DIR)/stage2/stage2_eltorito
$(ISO9660_TARGET_DIR)/boot/grub/ cp $(ISO9660_BOOT_MENU)
$(ISO9660_TARGET_DIR)/boot/grub/menu.lst cp
$(LINUX26_IMAGE_PATH) $(ISO9660_TARGET_DIR)/kernel cp
$(BINARIES_DIR)/rootfs.ext2 $(ISO9660_TARGET_DIR)/initrdI must admit that I'm not an user of this feature, so when I did the cleanup/rewrite of filesystem support, I left it as it was. Maybe it needs to work differently.
Regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com