Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #242107 > unrolled thread
| Started by | phoebus phoebus <frphoebus@yahoo.fr> |
|---|---|
| First post | 2021-11-13 01:40 +0100 |
| Last post | 2021-11-15 12:00 +0100 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
set the number of inodes during FS creation via pressed phoebus phoebus <frphoebus@yahoo.fr> - 2021-11-13 01:40 +0100
Re: set the number of inodes during FS creation via pressed Stanislav Vlasov <stanislav.v.v@gmail.com> - 2021-11-13 11:20 +0100
Re: set the number of inodes during FS creation via pressed David Wright <deblis@lionunicorn.co.uk> - 2021-11-13 18:20 +0100
Re: set the number of inodes during FS creation via pressed David <bouncingcats@gmail.com> - 2021-11-13 23:50 +0100
Re: set the number of inodes during FS creation via pressed phoebus phoebus <frphoebus@yahoo.fr> - 2021-11-14 15:00 +0100
Re: set the number of inodes during FS creation via pressed David Wright <deblis@lionunicorn.co.uk> - 2021-11-14 18:00 +0100
Re: set the number of inodes during FS creation via pressed David <bouncingcats@gmail.com> - 2021-11-15 01:50 +0100
Re: set the number of inodes during FS creation via pressed phoebus phoebus <frphoebus@yahoo.fr> - 2021-11-15 12:00 +0100
| From | phoebus phoebus <frphoebus@yahoo.fr> |
|---|---|
| Date | 2021-11-13 01:40 +0100 |
| Subject | set the number of inodes during FS creation via pressed |
| Message-ID | <DiPfk-3FU-5@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hello all,
Do you know if it possible to set the number of inodes to create in the filesystem during the installalation with the pressed file?
If i start from this example for the filesystem /var/log, how to set numbers of inodes inside it ?
500 550 1024 ext4 \ lv_name{ varlog } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
label{ varlog } \
mountpoint{ /var/log } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
options/relatime{ relatime } \
$lvmok{ } \
. \
Hope to do it as mkfs do it: mkfs -t ext4 -N iNumberOfINodes /dev/XdY ?
Thanks for your advise?
Regards,
Thierry
[toc] | [next] | [standalone]
| From | Stanislav Vlasov <stanislav.v.v@gmail.com> |
|---|---|
| Date | 2021-11-13 11:20 +0100 |
| Message-ID | <DiYiB-RW-1@gated-at.bofh.it> |
| In reply to | #242107 |
2021-11-13 5:31 GMT+05:00, phoebus phoebus <frphoebus@yahoo.fr>: > Do you know if it possible to set the number of inodes to create in the > filesystem during the installalation with the pressed file? You may try create fs in another console and use in without formatting. -- Stanislav
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-11-13 18:20 +0100 |
| Message-ID | <Dj4R4-4P7-5@gated-at.bofh.it> |
| In reply to | #242107 |
On Sat 13 Nov 2021 at 00:31:42 (+0000), phoebus phoebus wrote:
> Do you know if it possible to set the number of inodes to create in the filesystem during the installalation with the pressed file?
>
> If i start from this example for the filesystem /var/log, how to set numbers of inodes inside it ?
>
> 500 550 1024 ext4 \ lv_name{ varlog } \
> method{ lvm } format{ } \
> use_filesystem{ } filesystem{ ext4 } \
> label{ varlog } \
> mountpoint{ /var/log } \
> options/nodev{ nodev } \
> options/nosuid{ nosuid } \
> options/noexec{ noexec } \
> options/relatime{ relatime } \
> $lvmok{ } \
> . \
> Hope to do it as mkfs do it: mkfs -t ext4 -N iNumberOfINodes /dev/XdY ?
I don't know about the actual number, but I think there's a crude
switch under use_filesystem{ } which can be set, from memory,
to one of three options, Standard, large files (fewer inodes for,
say, multimedia) and lots of files (more inodes, say, mail server).
I've only seen the choice (years ago) in the interactive d-i,
and don't know the magic preseed terms.
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | David <bouncingcats@gmail.com> |
|---|---|
| Date | 2021-11-13 23:50 +0100 |
| Message-ID | <Dja0p-7MI-1@gated-at.bofh.it> |
| In reply to | #242137 |
On Sun, 14 Nov 2021 at 04:10, David Wright <deblis@lionunicorn.co.uk> wrote:
> On Sat 13 Nov 2021 at 00:31:42 (+0000), phoebus phoebus wrote:
> > Do you know if it possible to set the number of inodes to create in
> > the filesystem during the installalation with the pressed file?
> > If i start from this example for the filesystem /var/log, how to set
> > numbers of inodes inside it ?
> > 500 550 1024 ext4 \ lv_name{ varlog } \
> > method{ lvm } format{ } \
> > use_filesystem{ } filesystem{ ext4 } \
> > label{ varlog } \
> > mountpoint{ /var/log } \
> > options/nodev{ nodev } \
> > options/nosuid{ nosuid } \
> > options/noexec{ noexec } \
> > options/relatime{ relatime } \
> > $lvmok{ } \
> > . \
> > Hope to do it as mkfs do it: mkfs -t ext4 -N iNumberOfINodes /dev/XdY ?
> I don't know about the actual number, but I think there's a crude
> switch under use_filesystem{ } which can be set, from memory,
> to one of three options, Standard, large files (fewer inodes for,
> say, multimedia) and lots of files (more inodes, say, mail server).
> I've only seen the choice (years ago) in the interactive d-i,
> and don't know the magic preseed terms.
This site is quite useful:
https://preseed.debian.net/debian-preseed/
>From there I found this file for bullseye:
https://preseed.debian.net/debian-preseed/bullseye/amd64-main-full.txt
which contains this stanza which appears to match your description:
### Description: Typical usage of this partition:
# Please specify how the file system is going to be used, so that
# optimal file system parameters can be chosen for that use.
# .
# standard = standard parameters,
# news = one inode per 4KB block,
# largefile = one inode per megabyte,
# largefile4 = one inode per 4 megabytes.
# d-i partman-basicfilesystems/specify_usage select <choice>
# Possible choices: ${CHOICES}
Which is not what the OP requested, but maybe it helps. It is the only
occurrence of "inode" in that file. I did not check the other two files
that contain the "contrib" and "non-free" data.
[toc] | [prev] | [next] | [standalone]
| From | phoebus phoebus <frphoebus@yahoo.fr> |
|---|---|
| Date | 2021-11-14 15:00 +0100 |
| Message-ID | <Djod3-7Wr-9@gated-at.bofh.it> |
| In reply to | #242154 |
[Multipart message — attachments visible in raw view] — view raw
Thanks for the update.
>>From there I found this file for bullseye:>> https://preseed.debian.net/debian-preseed/bullseye/amd64-main-full.txt>>which contains this stanza which appears to match your description:
>>### Description: Typical usage of this partition:
>># Please specify how the file system is going to be used, so that>># optimal file system parameters can be chosen for that use.>># .>># standard = standard parameters,>># news = one inode per 4KB block,>># largefile = one inode per megabyte,>># largefile4 = one inode per 4 megabytes.>># d-i partman-basicfilesystems/specify_usage select <choice>>># Possible choices: ${CHOICES}>>>>Which is not what the OP requested, but maybe it helps. It is the only>>occurrence of "inode" in that file. I did not check the other two files>>that contain the "contrib" and "non-free" data.
I tryed to adapt like this with this option: **specify_usage{ }**
--------------------------------------------------------------------------------------------------------------
1024 1024 2048 ext4 \ lv_name{ var+log } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/log } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
$lvmok{ } \
. \
1024 1024 2048 ext4 \
lv_name{ var+loga } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/loga } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
specify_usage{ news } \
$lvmok{ } \
. \
1024 1024 2048 ext4 \
lv_name{ var+logb } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/logb } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
specify_usage{ large } \
$lvmok{ } \
. \
1024 1024 2048 ext4 \
lv_name{ var+logc } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/logc } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
specify_usage{ large4 } \
$lvmok{ } \
. \
1024 1024 2048 ext4 \
lv_name{ var+logd } \
method{ lvm } format{ } \
use_filesystem{ } filesystem{ ext4 } \
mountpoint{ /var/logd } \
options/nodev{ nodev } \
options/nosuid{ nosuid } \
options/noexec{ noexec } \
specify_usage{ standard } \
$lvmok{ } \
. \
--------------------------------------------------------------------------------------------------------------
But this change nothing after verfication the bytes per inode is 16k in all case. (<bytes-per-inode> = <block count> x <block size> / <inode count>)--------------------------------------------------------------------------------------------------------------
root@debian:~# dumpe2fs /dev/mapper/rootvg-var+log | grep -E "(Block count|Block size|Inode count)"
dumpe2fs 1.46.2 (28-Feb-2021)
Inode count: 62464
Block count: 249856
Block size: 4096
root@debian:~# dumpe2fs /dev/mapper/rootvg-var+loga | grep -E "(Block count|Block size|Inode count)"
dumpe2fs 1.46.2 (28-Feb-2021)
Inode count: 62464
Block count: 249856
Block size: 4096
root@debian:~# dumpe2fs /dev/mapper/rootvg-var+logb | grep -E "(Block count|Block size|Inode count)"
dumpe2fs 1.46.2 (28-Feb-2021)
Inode count: 62464
Block count: 249856
Block size: 4096
root@debian:~# dumpe2fs /dev/mapper/rootvg-var+logc | grep -E "(Block count|Block size|Inode count)"
dumpe2fs 1.46.2 (28-Feb-2021)
Inode count: 62464
Block count: 249856
Block size: 4096
root@debian:~# dumpe2fs /dev/mapper/rootvg-var+logd | grep -E "(Block count|Block size|Inode count)"
dumpe2fs 1.46.2 (28-Feb-2021)
Inode count: 62464
Block count: 249856
Block size: 4096
root@debian:~#--------------------------------------------------------------------------------------------------------------
Tryed also with
-----------------------------------------------------------------------------------------------------------d-i partman-basicfilesystems/specify_usage select news
----------------------------------------------------------------------------------------------------------
And ugly workaround will be to update inode_ration into /etc/mke2fs.conf with sed via
-------------------------------------------------------------------------------------------------------------------------
d-i partman/early_command string \ sed -i 's/inode_ratio = 16384/inode_ratio = 4096/g' /etc/mke2fs.conf
------------------------------------------------------------------------------------------------------------------------
but it apply to all FS.
/etc/mke2fs.con also indicates the values:
--------------------....
news = {
inode_ratio = 4096
}
largefile = {
inode_ratio = 1048576
blocksize = -1
}
largefile4 = {
inode_ratio = 4194304
blocksize = -1
}
.....
----------------------
I'll switch from EXT4 to XFS to not be worried about inodes defined at creation.
Unfortunaltely XFS don't take in charge the reduction but only the increase of FS size.
Don't be sure possibe to do "thin provisionning" and "thin pool" => Configure Thin Provision LVM with pressed as can be done with kickstarrt into RHEL.
Regards,
Thierry
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2021-11-14 18:00 +0100 |
| Message-ID | <Djr1f-1br-5@gated-at.bofh.it> |
| In reply to | #242171 |
On Sun 14 Nov 2021 at 13:32:45 (+0000), phoebus phoebus wrote:
> 1024 1024 2048 ext4 \
> lv_name{ var+logc } \
> method{ lvm } format{ } \
> use_filesystem{ } filesystem{ ext4 } \
> mountpoint{ /var/logc } \
> options/nodev{ nodev } \
> options/nosuid{ nosuid } \
> options/noexec{ noexec } \
> specify_usage{ large4 } \
> $lvmok{ } \
> . \
This is way beyond my experience. It's also not an area I'm reading up
on because I don't usually install into an empty drive or free space.
So I can only make one other suggestion, by extracting a few lines
from Appendix B of the Installation Guide:
# Or provide a recipe of your own...
# If you have a way to get a recipe file into the d-i environment, you can
# just point at it.
#d-i partman-auto/expert_recipe_file string /hd-media/recipe
ie, do that ↑, rather than this ↓
# If not, you can put an entire recipe into the preconfiguration file in one
# (logical) line. This example creates a small /boot partition, suitable
# swap, and uses the rest of the space for the root partition:
#d-i partman-auto/expert_recipe string \
# boot-root :: \
# 40 50 100 ext3 \
# $primary{ } $bootable{ } \
# method{ format } format{ } \
# use_filesystem{ } filesystem{ ext3 } \
# mountpoint{ /boot } \
# . \
# 500 10000 1000000000 ext3 \
Cheers,
David.
[toc] | [prev] | [next] | [standalone]
| From | David <bouncingcats@gmail.com> |
|---|---|
| Date | 2021-11-15 01:50 +0100 |
| Message-ID | <Djym5-5Ln-1@gated-at.bofh.it> |
| In reply to | #242171 |
On Mon, 15 Nov 2021 at 00:32, phoebus phoebus <frphoebus@yahoo.fr> wrote:
> Thanks for the update.
> >>From there I found this file for bullseye:
> >> https://preseed.debian.net/debian-preseed/bullseye/amd64-main-full.txt
> >>which contains this stanza which appears to match your description:
> I tryed to adapt like this with this option: **specify_usage{ }**
Hello,
Sorry, I do not have any additional knowledge about this.
But, I think you will have another chance to receive help
if you ask your entire question again on the mailing list for
discussion about the debian-install system:
https://lists.debian.org/debian-boot/
[toc] | [prev] | [next] | [standalone]
| From | phoebus phoebus <frphoebus@yahoo.fr> |
|---|---|
| Date | 2021-11-15 12:00 +0100 |
| Message-ID | <DjHSq-36h-7@gated-at.bofh.it> |
| In reply to | #242192 |
Hello, Thanks for the advice. Le lundi 15 novembre 2021, 01:40:46 UTC+1, David <bouncingcats@gmail.com> a écrit : >> Hello, >> >>Sorry, I do not have any additional knowledge about this. >>But, I think you will have another chance to receive help >>if you ask your entire question again on the mailing list for >>discussion about the debian-install system: >> https://lists.debian.org/debian-boot/ I sent an email to the list with the subject: "set the number of inodes during FS creation via pressed (specify_usage)" Regards, Thierry
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web