Kernel 6.1.0-50 for daedalus got a bug it seems...

greenjeans · Today 19:05:56

Went to update the Vuu-do mini yesterday, it was using 6.1.0-49. Some 40+ updates including the new kernel. (linux-image-amd64 (6.1.174-1) to 6.1.176-1)

After installing I first noticed the issue in my conky display, it was underreporting disk space used by about 400 mb with the new kernel. Running df -h showed the same issue. It's a fact that this system installed is about ~2.7 gb or a little less, yet it's showing 2.27 gb in conky (fs_used) and 2.3 from the df command.

Seems it must be the kernel as the other updates don't seem to have anything to do with it. (mostly imagemagick, python, mesa, image and compression libraries).

Wonder what happened? Did it get some rust on it, lol?

fsmithred · Today 21:02:24

I'm not seeing much difference in df output with 6.1.0-48 vs. 6.1.0-50 and also 7.1.3 in freia. Only about 1-2mb difference. Try it without the '-h'.

/dev/mapper/root_fs		199450960 137851664  6.1.0-50
/dev/mapper/root_fs		199450960 137850896  6.1.0-48
/dev/mapper/sda4_crypt	        199450960 137853112  7.x

/dev/sda5			29367400  24062932  6.1.0-50
/dev/sda5			29367400  24062712  6.1.0-48
/dev/sda5			29367400  24060396  7.1.3

Altoid · Today 21:12:10

Hello:

greenjeans wrote:

... yet it's showing 2.27 gb in conky (fs_used) and 2.3 from the df command.

Me thinks [df -h] is rounding out.
Maybe there is a switch to make it give you decimal numbers?

I haven't found anything save using a script to parse.

This is on [Daedalus] after the last large update / upgrade:

$
uname -a
Linux devuan 6.1.0-50-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.176-1 (2026-07-02) x86_64 GNU/Linux
$

$ df -h
Filesystem      Size  Used Avail Use% Mounted on                             
/dev/sda1        40G  9.9G   30G  26% /                 # conky reports 9.86GiB / 39.1GiB 
/dev/sda5       705M   26M  626M   4% /var/log          # conky reports 25.8MiB / 704MiB
/dev/sda6        68G   31G   37G  46% /home             # conky reports 30.5GiB / 67.3GiB    
/dev/sdb2        67G   38G   25G  61% /media/1TB/TS     # conky reports 37.8GiB / 66.2GiB
/dev/sdb1       849G  701G  107G  87% /media/1TB/IMG    # conky reports 700GiB / 849GiB
$

Just found this:
https://computingforgeeks.com/check-dis … -with-duf/

# duf
╭───────────────────────────────────────────────────────────────────────────────────────────────╮
│ 8 local devices                                                                               │
├────────────────┬────────┬────────┬────────┬───────────────────────────────┬──────┬────────────┤
│ MOUNTED ON     │   SIZE │   USED │  AVAIL │              USE%             │ TYPE │ FILESYSTEM │
├────────────────┼────────┼────────┼────────┼───────────────────────────────┼──────┼────────────┤
│ /              │  39.1G │   9.9G │  29.1G │ [#####...............]  25.2% │ ext4 │ /dev/sda1  │
│ /home          │  67.3G │  30.5G │  36.8G │ [#########...........]  45.3% │ ext4 │ /dev/sda6  │
│ /media/1TB/IMG │ 848.5G │ 700.3G │ 106.4G │ [################....]  82.5% │ ext4 │ /dev/sdb1  │
│ /media/1TB/TS  │  66.2G │  38.2G │  24.6G │ [###########.........]  57.7% │ ext4 │ /dev/sdb2  │
│ /media/300GBIT │ 273.9G │ 143.4G │ 116.5G │ [##########..........]  52.4% │ ext4 │ /dev/sdf1  │
│ /media/storage │ 273.9G │ 146.3G │ 113.7G │ [##########..........]  53.4% │ ext4 │ /dev/sdd1  │
│ /media/stuff   │  66.7G │  20.6G │  42.7G │ [######..............]  30.9% │ ext4 │ /dev/sde1  │
│ /var/log       │ 704.3M │  25.8M │ 626.0M │ [....................]   3.7% │ ext4 │ /dev/sda5  │
╰────────────────┴────────┴────────┴────────┴───────────────────────────────┴──────┴────────────╯
╭───────────────────────────────────────────────────────────────────────────────────────────────────╮
│ 6 special devices                                                                                 │
├────────────────┬────────┬────────┬────────┬───────────────────────────────┬──────────┬────────────┤
│ MOUNTED ON     │   SIZE │   USED │  AVAIL │              USE%             │ TYPE     │ FILESYSTEM │
├────────────────┼────────┼────────┼────────┼───────────────────────────────┼──────────┼────────────┤
│ /dev           │   3.8G │     0B │   3.8G │                               │ devtmpfs │ udev       │
│ /dev/shm       │   2.1G │     0B │   2.1G │                               │ tmpfs    │ tmpfs      │
│ /run           │ 787.5M │ 808.0K │ 786.7M │ [....................]   0.1% │ tmpfs    │ tmpfs      │
│ /run/lock      │   5.0M │   8.0K │   5.0M │ [....................]   0.2% │ tmpfs    │ tmpfs      │
│ /run/user/1000 │ 787.5M │   8.0K │ 787.5M │ [....................]   0.0% │ tmpfs    │ tmpfs      │
│ /sys/fs/cgroup │   3.8G │     0B │   3.8G │                               │ tmpfs    │ cgroup     │
╰────────────────┴────────┴────────┴────────┴───────────────────────────────┴──────────┴────────────╯
#

Screen output is in decimals, colour and apparently configurable.
Niiiice ...

Best,

A.

Edit:
Fixed [/dev/sdb1] and [/dev/sdb2] that had printout swapped.

Last edited by Altoid (Today 22:25:37)

greenjeans · Today 22:05:45

Trust me it's there. And i've used every command imaginable, df, du, dumpe2fs etc.

Possibly something in my hardware as always, but I have two other partitions on 49 and they are reporting correctly while the 50 partition is stating that it's 400 mb less than what it really is. This system has been in maintenance mode for months as it's stable and works as intended, so i've just been doing updates when there's a kernel update and/or important security updates. At those times I do a little tweaking and sometimes add a little, this time I added VuuMan and the Lightdm settings editor, less than a mb but it should have added to the total. It's been stable at around 2.65-2.7 gb's for some 8 months and was at 2.66 before the updates.

In the file manager on any of the partitions you can right-click and choose "properties" and it simple adds up all the files and sizes and they are all reporting that it's around 2.7 gb. I ran Refracta-snapshot and it firsts makes a copy of the running system and the total of that is reflected in the terminal it's running in, and it also says 2.7 gb.

EDIT: Oh forgot to mention, the snapshot I ran came out to be exactly the same size plus a couple of kb, as the last snapshot I did before I swapped in the new kernel. If the system really was 400 mb smaller is should have resulted in around 120-140 mb smaller iso. It's the same size.

There is nothing I did during updates that could have possibly saved me 400 mb, lol, i'll post the log of what I did. This is a bug of some kind.

Commit Log for Sat Jul 11 17:32:27 2026

Upgraded the following packages:
imagemagick (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
imagemagick-6-common (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
imagemagick-6.q16 (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
libcaca0 (0.99.beta20-3) to 0.99.beta20-3+deb12u1
libcurl3-gnutls (7.88.1-10+deb12u14) to 7.88.1-10+deb12u15
libcurl4 (7.88.1-10+deb12u14) to 7.88.1-10+deb12u15
libegl-mesa0 (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libgbm1 (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libgif7 (5.2.1-2.5) to 5.2.1-2.5+deb12u1
libgl1-mesa-dri (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libglapi-mesa (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libglx-mesa0 (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libgraphite2-3 (1.3.14-1) to 1.3.14-1+deb12u1
libhtml-parser-perl (3.81-1) to 3.81-1+deb12u1
libhttp-daemon-perl (6.16-1) to 6.16-1+deb13u1~deb12u1
libinput-bin (1.22.1-1) to 1.22.1-1+deb12u1
libinput10 (1.22.1-1) to 1.22.1-1+deb12u1
liblzma5 (5.4.1-1) to 5.4.1-1+deb12u1
libmagickcore-6.q16-6 (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
libmagickcore-6.q16-6-extra (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
libmagickwand-6.q16-6 (8:6.9.11.60+dfsg-1.6+deb12u10) to 8:6.9.11.60+dfsg-1.6+deb12u11
libpoppler-glib8 (22.12.0-2+deb12u1) to 22.12.0-2+deb12u2
libpoppler126 (22.12.0-2+deb12u1) to 22.12.0-2+deb12u2
libpython3.11 (3.11.2-6+deb12u7) to 3.11.2-6+deb12u8
libpython3.11-minimal (3.11.2-6+deb12u7) to 3.11.2-6+deb12u8
libpython3.11-stdlib (3.11.2-6+deb12u7) to 3.11.2-6+deb12u8
librabbitmq4 (0.11.0-1+deb12u1) to 0.11.0-1+deb12u2
libssl3 (3.0.20-1~deb12u1) to 3.0.20-1~deb12u2
libxatracker2 (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
libxml2 (2.9.14+dfsg-1.3~deb12u5) to 2.9.14+dfsg-1.3~deb12u6
linux-base (4.9) to 4.12.1~deb12u1
linux-image-amd64 (6.1.174-1) to 6.1.176-1
mesa-va-drivers (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
mesa-vdpau-drivers (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
mesa-vulkan-drivers (22.3.6-1+deb12u1) to 22.3.6-1+deb12u2
openssl (3.0.20-1~deb12u1) to 3.0.20-1~deb12u2
p7zip (16.02+really25.01+dfsg-0+deb12u1) to 16.02+really26.01+dfsg-0+deb12u1
p7zip-full (16.02+really25.01+dfsg-0+deb12u1) to 16.02+really26.01+dfsg-0+deb12u1
poppler-utils (22.12.0-2+deb12u1) to 22.12.0-2+deb12u2
python3-urllib3 (1.26.12-1+deb12u3) to 1.26.12-1+deb12u4
python3.11 (3.11.2-6+deb12u7) to 3.11.2-6+deb12u8
python3.11-minimal (3.11.2-6+deb12u7) to 3.11.2-6+deb12u8
rsync (3.2.7-1+deb12u5) to 3.2.7-1+deb12u6
wireless-regdb (2026.02.04-1~deb12u1) to 2026.05.30-1~deb12u1
xz-utils (5.4.1-1) to 5.4.1-1+deb12u1

Installed the following packages:
lightdm-gtk-greeter-settings (1.2.2-5)
linux-image-6.1.0-50-amd64 (6.1.176-1)

Commit Log for Sat Jul 11 18:06:17 2026

Completely removed the following packages:
linux-image-6.1.0-49-amd64

Last edited by greenjeans (Today 22:13:16)

greenjeans · Today 22:26:27

The size is right about the size of the kernel itself...maybe they changed the way it reports disk usage to omit the kernel itself from the total. I was up last night until 2:00 a.m testing, and resumed doing so earlier today to rule out anything else.

ralph.ronnquist · Today 23:46:02

The kernel doesn't report disk usage. All raw figures are in filesystem meta data. Use dumpefs and stat to see them (other filesystem types than ext4 may have similar metadata access; there's always hexdump to go crazy with raw data).

There are many metadata number involved, and it's generally difficult to decide for each, whether and how it enters into a usage calculation. Perhaps the reporting program(s) with such calculations have changed? It won't be in the kernel, though.

The officially official Devuan Forum!

#1 Today 19:05:56

Kernel 6.1.0-50 for daedalus got a bug it seems...

#2 Today 21:02:24

Re: Kernel 6.1.0-50 for daedalus got a bug it seems...

#3 Today 21:12:10

Re: Kernel 6.1.0-50 for daedalus got a bug it seems...

#4 Today 22:05:45

Re: Kernel 6.1.0-50 for daedalus got a bug it seems...

#5 Today 22:26:27

Re: Kernel 6.1.0-50 for daedalus got a bug it seems...

#6 Today 23:46:02

Re: Kernel 6.1.0-50 for daedalus got a bug it seems...

Board footer