> On 21.10.2016, at 17:20, Andre Valentin <avalen...@marcant.net> wrote: > > Hi! > > Am 21.10.2016 um 10:33 schrieb Felix Fietkau: >>> I have switched rootfs now to squashfs, that ist working. But I have >>> problems with the overlayfs. >>> It is on /dev/mmcblk0p1, but I do not understand how to tell the system to >>> use this partition. I cannot find a matching example. >>> >>> What I did: >>> 1) Added an fstab to the squassh image: >>> config 'global' >>> option anon_swap '0' >>> option anon_mount '0' >>> option auto_swap '1' >>> option auto_mount '1' >>> option delay_root '5' >>> option check_fs '0' >>> >>> config 'mount' >>> option device '/dev/mmcblk0p1' >>> option enabled '1' >>> option target '/overlay' >>> option fstype 'ext4' >>> option options 'rw,sync' >>> option enabled_fsck 0 >>> option is_rootfs '1' >>> >>> 2) label the ext4fs rootfs_data >>> 3) added rootfs_data=/dev/mmcblk0p1 on kernel commandline. >>> >>> But fstools does not mount it. >>> Please help. >> Don't put overlay mount stuff in the config. Make sure you have >> e2fsprogs and mkf2fs enabled in your config and that the rootfs >> partition is big enough to fit both the squashfs image and the overlay >> filesystem. > I tried that but it is an EFI partition not an mtd partition. To my > understanding, > only mtd partitons will be split into rootfs and rootfs_data on boot. > This does not hapen. I need a way to tell the system that /dev/mmcblk0p1 is > my overlay FS. > Is there a possibility that I can somehow tell fstools which fs to use for > overlay. Or which > depencies are there for detecting that an device holds an fs for overlay? The overlay split is handled in user space by fstools. Try enabling loopback device support in the kernel config
- Felix _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
