On 2016-11-22 23:48, Bastian Bittorf wrote:
> * Bastian Bittorf [22.11.2016 23:47]:
>> answer myself: CONFIG_TARGET_ROOTFS_PARTSIZE is unset?
>>
>> see 'Image/Build/squashfs' in 'uml/Image/Makefile'
>
> indeed, it works when i set it manually and i can boot into UML:
I updated the commit to allo
* Bastian Bittorf [22.11.2016 23:47]:
> answer myself: CONFIG_TARGET_ROOTFS_PARTSIZE is unset?
>
> see 'Image/Build/squashfs' in 'uml/Image/Makefile'
indeed, it works when i set it manually and i can boot into UML:
root@uml:/ df -h
FilesystemSize Used Available Use% Mounted
* Bastian Bittorf [22.11.2016 23:01]:
> * Felix Fietkau [22.11.2016 22:42]:
> > > here the build-error with "inodes full".
> > > (the same images works, if i just raise the inodes to 2048)
> > Try disabling the ext4 image via make menuconfig.
>
> sorry, does not help. i did:
> make menuconfig (u
* Felix Fietkau [22.11.2016 22:42]:
> > here the build-error with "inodes full".
> > (the same images works, if i just raise the inodes to 2048)
> Try disabling the ext4 image via make menuconfig.
sorry, does not help. i did:
make menuconfig (unselect ext4)
make clean
make BUILD_LOG=1
(build abor
On 2016-11-22 21:28, Bastian Bittorf wrote:
> * Felix Fietkau [22.11.2016 18:17]:
>> > I tested it and it's usable with 16M rootfs.
>> Here's some more information: it creates the overlay filesystem with a
>> block size of 1K, and it has 3493 free inodes after booting up.
>
> Does not work here,
* Felix Fietkau [22.11.2016 18:17]:
> > I tested it and it's usable with 16M rootfs.
> Here's some more information: it creates the overlay filesystem with a
> block size of 1K, and it has 3493 free inodes after booting up.
Does not work here, with some additional packages (like olsrd + olsrd2
+r
On 2016-11-22 18:04, Felix Fietkau wrote:
> On 2016-11-22 17:57, David Lang wrote:
>> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>>
>>> On 2016-11-22 17:48, David Lang wrote:
On Tue, 22 Nov 2016, Felix Fietkau wrote:
> On 2016-11-22 17:43, David Lang wrote:
>> On Tue, 22 Nov 2016,
On 2016-11-22 17:57, David Lang wrote:
> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>
>> On 2016-11-22 17:48, David Lang wrote:
>>> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>>>
On 2016-11-22 17:43, David Lang wrote:
> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>
>>> On a 16M filesy
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On 2016-11-22 17:48, David Lang wrote:
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On 2016-11-22 17:43, David Lang wrote:
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On a 16M filesystem, we probably want to use a 1K block size and have an inode
for eve
On 2016-11-22 17:43, David Lang wrote:
> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>
>>> On a 16M filesystem, we probably want to use a 1K block size and have an
>>> inode
>>> for every couple of blocks.
>> I'd say on a 16M filesystem we probably want to use squashfs+ext4
>> instead of plain ext4
On 2016-11-22 17:48, David Lang wrote:
> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>
>> On 2016-11-22 17:43, David Lang wrote:
>>> On Tue, 22 Nov 2016, Felix Fietkau wrote:
>>>
> On a 16M filesystem, we probably want to use a 1K block size and have an
> inode
> for every couple of blo
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On 2016-11-22 17:43, David Lang wrote:
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On a 16M filesystem, we probably want to use a 1K block size and have an inode
for every couple of blocks.
I'd say on a 16M filesystem we probably want to use squashfs+e
On Tue, 22 Nov 2016, Felix Fietkau wrote:
On a 16M filesystem, we probably want to use a 1K block size and have an inode
for every couple of blocks.
I'd say on a 16M filesystem we probably want to use squashfs+ext4
instead of plain ext4 and avoid the inode issue altogether.
I'm not sure I und
On 2016-11-22 15:41, David Lang wrote:
> changing the blocksize doesn't really address the problem of too few inodes,
> except indirectly in that the default number of inodes is calculated from the
> number of blocks on the filesystem.
>
> In the case of LEDE, we tend to have fewer large files o
On Tue, 22 Nov 2016, Jo-Philipp Wich wrote:
1)
detect via makefile if PARTITION is small and autoadjust BLOCKSIZE
(if not given)
iirc the blocksize setting is a choice menu, so it is always defined.
2)
set BLOCKSIZE default to 1K via x86/UML-Makefile
It was explicitly raised to 4k for x86
Hi,
> 1)
> detect via makefile if PARTITION is small and autoadjust BLOCKSIZE
> (if not given)
iirc the blocksize setting is a choice menu, so it is always defined.
> 2)
> set BLOCKSIZE default to 1K via x86/UML-Makefile
It was explicitly raised to 4k for x86 to reduce wear on MMC storage
which
* Jo-Philipp Wich [22.11.2016 10:08]:
> a huge block size on small partition simply makes no sense. If you
> already configure 16MB partitions then you can as well change block size
> from 4K to 1K or 512B as well since you're deviating from the defaults
> anyway.
>
> Having different code paths
Hi,
a huge block size on small partition simply makes no sense. If you
already configure 16MB partitions then you can as well change block size
from 4K to 1K or 512B as well since you're deviating from the defaults
anyway.
Having different code paths for small and huge partitions is annoying
and
* John Crispin [21.11.2016 16:06]:
>
>
> On 21/11/2016 13:56, John Crispin wrote:
> > NAK, please dont fiddle with inode counts. change the blocksize or the
> > default mkfs_ext4 uses.
thanks for your input.
But i'am unsure now: when changing the blocksize
("CONFIG_TARGET_EXT4_BLOCKSIZE")
I h
On 21/11/2016 13:56, John Crispin wrote:
> NAK, please dont fiddle with inode counts. change the blocksize or the
> default mkfs_ext4 uses.
>
> John
https://git.lede-project.org/?p=project/make_ext4fs.git;a=blob;f=make_ext4fs.c#l281
>
> On 12/11/2016 09:26, Bastian Bittorf wrote:
>> A
NAK, please dont fiddle with inode counts. change the blocksize or the
default mkfs_ext4 uses.
John
On 12/11/2016 09:26, Bastian Bittorf wrote:
> A rootfs typically has lots of small files, so the default
> counter with 1024 inodes for 16 megabytes partition size can
> be too restrictive
* Bastian Bittorf [12.11.2016 09:54]:
> +# doubles the default inode amount
> +INODES=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*64*2)))
> E2SIZE=$(shell echo $$(($(CONFIG_TARGET_ROOTFS_PARTSIZE)*1024*1024)))
bye the way:
i mimic'ed the existing style, but is'nt this too much?
can't this
A rootfs typically has lots of small files, so the default
counter with 1024 inodes for 16 megabytes partition size can
be too restrictive and leads to e.g.
root@box:/ touch /etc/config/test
touch: /etc/config/test: No space left on device
the solution is to just double the amount of inodes
durin
23 matches
Mail list logo
