search

kdave / btrfs-progs

Development of userspace BTRFS tools
GNU General Public License v2.0
546 stars 240 forks source link

btrfs-progs v5.18: convert-tests/017-fs-near-full (x86, 32bit) #251

Open ernsteiswuerfel opened 4 years ago

ernsteiswuerfel commented 4 years ago

btrfs-progs was built from current git-master.

=== START TEST /root/build/btrfs-progs/tests/cli-tests/014-multiple-profiles-warning
====== RUN CHECK losetup --find --show img1
/dev/loop8
====== RUN CHECK losetup --find --show img2
/dev/loop9
====== RUN CHECK losetup --find --show img3
/dev/loop10
====== RUN CHECK losetup --find --show img4
/dev/loop11
====== RUN CHECK /root/build/btrfs-progs/mkfs.btrfs -f -d single -m single /dev/loop8 /dev/loop9 /dev/loop10 /dev/loop11
btrfs-progs v5.6.1 
See http://btrfs.wiki.kernel.org for more information.

Label:              (null)
UUID:               48e30c7f-a056-475b-96b0-2f42ba7551ab
Node size:          16384
Sector size:        4096
Filesystem size:    8.00GiB
Block group profiles:
  Data:             single            8.00MiB
  Metadata:         single            8.00MiB
  System:           single            4.00MiB
SSD detected:       yes
Incompat features:  extref, skinny-metadata
Checksum:           crc32c
Number of devices:  4
Devices:
   ID        SIZE  PATH
    1     2.00GiB  /dev/loop8
    2     2.00GiB  /dev/loop9
    3     2.00GiB  /dev/loop10
    4     2.00GiB  /dev/loop11

====== RUN CHECK mount -t btrfs /dev/loop8 /root/build/btrfs-progs/tests/mnt
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem usage /root/build/btrfs-progs/tests/mnt
Overall:
    Device size:           8.00GiB
    Device allocated:         20.00MiB
    Device unallocated:        7.98GiB
    Device missing:          0.00B
    Used:            128.00KiB
    Free (estimated):          7.99GiB  (min: 7.99GiB)
    Data ratio:               1.00
    Metadata ratio:           1.00
    Global reserve:        3.25MiB  (used: 0.00B)
    Multiple profiles:              no

Data,single: Size:8.00MiB, Used:0.00B (0.00%)
   /dev/loop8      8.00MiB

Metadata,single: Size:8.00MiB, Used:112.00KiB (1.37%)
   /dev/loop8      8.00MiB

System,single: Size:4.00MiB, Used:16.00KiB (0.39%)
   /dev/loop8      4.00MiB

Unallocated:
   /dev/loop8      1.98GiB
   /dev/loop9      2.00GiB
   /dev/loop10     2.00GiB
   /dev/loop11     2.00GiB
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file1 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file2 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file3 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file4 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file5 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file6 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file7 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file8 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file9 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file10 bs=100M count=1 status=none
====== RUN CHECK /root/build/btrfs-progs/btrfs balance start -dconvert=raid1,limit=1 /root/build/btrfs-progs/tests/mnt
Done, had to relocate 1 out of 6 chunks
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem usage /root/build/btrfs-progs/tests/mnt
Overall:
    Device size:           8.00GiB
    Device allocated:          2.71GiB
    Device unallocated:        5.29GiB
    Device missing:          0.00B
    Used:              1.13GiB
    Free (estimated):          4.41GiB  (min: 3.52GiB)
    Data ratio:               1.50
    Metadata ratio:           1.00
    Global reserve:        3.25MiB  (used: 0.00B)
    Multiple profiles:             yes  (data)

Data,single: Size:840.00MiB, Used:839.61MiB (99.95%)
   /dev/loop8      8.00MiB
   /dev/loop9    832.00MiB

Data,RAID1: Size:832.00MiB, Used:161.02MiB (19.35%)
   /dev/loop8    832.00MiB
   /dev/loop10   832.00MiB

Metadata,single: Size:264.00MiB, Used:1.25MiB (0.47%)
   /dev/loop8      8.00MiB
   /dev/loop10   256.00MiB

System,single: Size:4.00MiB, Used:16.00KiB (0.39%)
   /dev/loop8      4.00MiB

Unallocated:
   /dev/loop8      1.17GiB
   /dev/loop9      1.19GiB
   /dev/loop10   960.00MiB
   /dev/loop11     2.00GiB
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem df /root/build/btrfs-progs/tests/mnt
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
====== RUN CHECK /root/build/btrfs-progs/btrfs device delete /dev/loop11 /root/build/btrfs-progs/tests/mnt
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
====== RUN CHECK /root/build/btrfs-progs/btrfs device add -f /dev/loop11 /root/build/btrfs-progs/tests/mnt
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
====== RUN CHECK /root/build/btrfs-progs/btrfs device usage /root/build/btrfs-progs/tests/mnt
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
====== RUN MAYFAIL /root/build/btrfs-progs/btrfs balance pause /root/build/btrfs-progs/tests/mnt
failed (ignored, ret=2): /root/build/btrfs-progs/btrfs balance pause /root/build/btrfs-progs/tests/mnt
ERROR: balance pause on '/root/build/btrfs-progs/tests/mnt' failed: Not running
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
WARNING:   Data: single, raid1
====== RUN MAYFAIL /root/build/btrfs-progs/btrfs balance cancel /root/build/btrfs-progs/tests/mnt
failed (ignored, ret=2): /root/build/btrfs-progs/btrfs balance cancel /root/build/btrfs-progs/tests/mnt
ERROR: balance cancel on '/root/build/btrfs-progs/tests/mnt' failed: Not in progress
WARNING: Multiple block group profiles detected, see 'man btrfs(5)'.
WARNING:   Data: single, raid1
====== RUN CHECK umount /dev/loop8
====== RUN CHECK /root/build/btrfs-progs/mkfs.btrfs -f --mixed -d single -m single /dev/loop8 /dev/loop9 /dev/loop10 /dev/loop11
btrfs-progs v5.6.1 
See http://btrfs.wiki.kernel.org for more information.

Label:              (null)
UUID:               6ad2b7bf-7625-4fb4-8103-36dab2029e7f
Node size:          4096
Sector size:        4096
Filesystem size:    8.00GiB
Block group profiles:
  Data+Metadata:    single            8.00MiB
  System:           single            4.00MiB
SSD detected:       yes
Incompat features:  mixed-bg, extref, skinny-metadata
Checksum:           crc32c
Number of devices:  4
Devices:
   ID        SIZE  PATH
    1     2.00GiB  /dev/loop8
    2     2.00GiB  /dev/loop9
    3     2.00GiB  /dev/loop10
    4     2.00GiB  /dev/loop11

====== RUN CHECK mount -t btrfs /dev/loop8 /root/build/btrfs-progs/tests/mnt
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem usage /root/build/btrfs-progs/tests/mnt
Overall:
    Device size:           8.00GiB
    Device allocated:         12.00MiB
    Device unallocated:        7.99GiB
    Device missing:          0.00B
    Used:             32.00KiB
    Free (estimated):          8.00GiB  (min: 8.00GiB)
    Data ratio:               1.00
    Metadata ratio:           1.00
    Global reserve:      832.00KiB  (used: 0.00B)
    Multiple profiles:              no

Data+Metadata,single: Size:8.00MiB, Used:28.00KiB (0.34%)
   /dev/loop8      8.00MiB

System,single: Size:4.00MiB, Used:4.00KiB (0.10%)
   /dev/loop8      4.00MiB

Unallocated:
   /dev/loop8      1.99GiB
   /dev/loop9      2.00GiB
   /dev/loop10     2.00GiB
   /dev/loop11     2.00GiB
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file1 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file2 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file3 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file4 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file5 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file6 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file7 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file8 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file9 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file10 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file11 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file12 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file13 bs=100M count=1 status=none
====== RUN CHECK dd if=/dev/zero of=/root/build/btrfs-progs/tests/mnt/file14 bs=100M count=1 status=none
====== RUN CHECK /root/build/btrfs-progs/btrfs balance start -mconvert=raid1,usage=50 -dconvert=raid1,usage=50 /root/build/btrfs-progs/tests/mnt
Done, had to relocate 1 out of 4 chunks
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem usage /root/build/btrfs-progs/tests/mnt
Overall:
    Device size:           8.00GiB
    Device allocated:          1.70GiB
    Device unallocated:        6.30GiB
    Device missing:          0.00B
    Used:              1.37GiB
    Free (estimated):          6.57GiB  (min: 3.41GiB)
    Data ratio:               1.00
    Metadata ratio:           1.00
    Global reserve:        1.52MiB  (used: 0.00B)
    Multiple profiles:              no

Data+Metadata,single: Size:1.63GiB, Used:1.37GiB (83.85%)
   /dev/loop8      8.00MiB
   /dev/loop9    832.00MiB
   /dev/loop11   832.00MiB

System,RAID1: Size:32.00MiB, Used:4.00KiB (0.01%)
   /dev/loop8     32.00MiB
   /dev/loop10    32.00MiB

Unallocated:
   /dev/loop8      1.96GiB
   /dev/loop9      1.19GiB
   /dev/loop10     1.97GiB
   /dev/loop11     1.19GiB
====== RUN CHECK /root/build/btrfs-progs/btrfs filesystem df /root/build/btrfs-progs/tests/mnt
System, RAID1: total=32.00MiB, used=4.00KiB
Data+Metadata, single: total=1.63GiB, used=1.37GiB
GlobalReserve, single: total=1.52MiB, used=0.00B
filesystem df does not warn
test failed for case 014-multiple-profiles-warning

Some data about the machine:

 # inxi -b
System:    Kernel: 5.7.0-rc6-Pentium4 i686 bits: 32 Console: tty 1 
           Distro: Gentoo Base System release 2.6 
Machine:   Type: Desktop Mobo: Shuttle model: FS51 serial: N/A BIOS: Phoenix v: 6.00 PG 
           date: 12/02/2003 
CPU:       Single Core: Intel Pentium 4 type: MCP speed: 2796 MHz 
Graphics:  Device-1: AMD RV350 [Radeon 9550/9600/X1050 Series] driver: N/A 
           Display: server: X.org 1.20.7 driver: modesetting tty: 104x53 
           Message: Advanced graphics data unavailable in console for root. 
Network:   Device-1: Ralink RT2500 Wireless 802.11bg driver: rt2500pci
kdave commented 4 years ago

Thanks for the report, so the guesswork to create the filesystem with multiple mixed profiles does not work on your version 5.7 or it maybe depends on the underlying devices too. I'm testing that on 5.5 and netowrk backed disk and the test passes.

ernsteiswuerfel commented 4 years ago

Same error on my PowerMac G4 too (kernel 5.7-rc7 and 5.6.14). Device on the G4 would be a SATA-SSD connected to a SiL3112. On the Pentium4 it is a HDD connected to internal IDE. G4_cli-tests-results.txt

ernsteiswuerfel commented 4 years ago

Re-test with btrfs-progs v5.7 and kernel 5.8-rc5 on x86 (Pentium4, 32bit) too. Turns out exactly the same tests fail on ppc and x86, 32bit. So I will close the newer ppc-specific issue #262 in favour of this one as it's the older bug reported.

marcosps commented 4 years ago

@ernsteiswuerfel I found a git commit that introduced this behavior change for fsck-test/037, and I'm now preparing a patch to submit to my peers. I believe this is a regression, but let's see how it goes when they review the patch.

Thanks again for submitting these reports, and for waiting for us to fix them :)

marcosps commented 4 years ago

@adam900710 what do you think about https://github.com/marcosps/linux/commit/12084186851d519d0401060e683d1fb469e64880 ? it fixes fsck/037 for me. let me know if you agree with the change. If yes, I'll send to the ML :)

adam900710 commented 4 years ago

@marcosps You're right! It's my fault to cause the regression.

Great fix!

marcosps commented 4 years ago

@marcosps You're right! It's my fault to cause the regression.

Great fix!

Thanks :) Patch sent to ML

marcosps commented 4 years ago

@ernsteiswuerfel can you please retry convert/017 again with the current devel branch? There were some changes regarding convert, specially 38f220d6eea51344603e5a213c21500ec671b8b8, which can help us to detect if the problem happened in the kernel side or in the convert tool itself.

At least it didn't fail for me using a more recent devel branch.

marcosps commented 4 years ago

@ernsteiswuerfel same goes for cli-test/014, there are some patches in devel that should address the multiple profiles detection. Can you please test again? Thanks in advance for your work!

ernsteiswuerfel commented 4 years ago

For me these tests still fail unfortunately. Did run the tests specifically, kernel 5.8.3 on the G4. Built btrfs-progs from devel ce6e0f572f44c46e57e3c19bdd9105e2ab2bf296. fsck-tests-results.txt convert-tests-results.txt cli-tests-results.txt

marcosps commented 4 years ago

For me these tests still fail unfortunately. Did run the tests specifically, kernel 5.8.3 on the G4. Built btrfs-progs from devel ce6e0f572f44c46e57e3c19bdd9105e2ab2bf296. fsck-tests-results.txt

This one is indeed prone to fail since the kernel patch is missing. Would you like to test the latest version of the patch and then reexecute btrfsprogs tests on it? Also, if you do, you could add a tested-by tag in the kernel patch: https://lore.kernel.org/linux-btrfs/20200821145444.25791-1-marcos@mpdesouza.com/T/#u

convert-tests-results.txt The first thing that I can spot right by checking your report is that the same test on my machine reports different free space: free: 49676288 (4.63%) Which is 10Mb bigger than yours: free: 39124992 (3.64%)

@adam900710 do you have any idea if different archs should report different usage? The result for me is the same using v.5.8.3 or running misc-next, and it works.

cli-tests-results.txt In this case, the balance didn't manage to convert some of the single block groups to raid1. For me it relocated two chunks:

Done, had to relocate 2 out of 4 chunks

That explains why the test fails and will require more investigation on kernel side, as for me it works testing on misc-next and in v5.8.3 and it works =/

ernsteiswuerfel commented 4 years ago

Applied 101ea93 on top of kernel 5.9-rc2 and fsck-tests/037-freespacetree-repair passes now on the G4. Thanks!

ernsteiswuerfel commented 4 years ago

The first thing that I can spot right by checking your report is that the same test on my machine reports different free space: free: 49676288 (4.63%) Which is 10Mb bigger than yours: free: 39124992 (3.64%)

@adam900710 do you have any idea if different archs should report different usage? The result for me is the same using v.5.8.3 or running misc-next, and it works.

convert-tests/017-fs-near-full passes too now, but don't know whether it's the patch or 5.9-rc2 by itself. I could test this out when it is of some interest? Anyway now this test is working it also reports 

====== RUN CHECK /root/build/btrfs-progs/btrfs-convert /root/build/btrfs-progs/tests/test.img
create btrfs filesystem:
        blocksize: 4096
        nodesize:  16384
        features:  extref, skinny-metadata (default)
        checksum:  crc32c
free space report:
        total:     1073741824
        free:      49676288 (4.63%)

on the G4. cli-tests/014-multiple-profiles-warning still fails.

marcosps commented 4 years ago

@ernsteiswuerfel great. For the fsck/037, this is expected. Thanks for testing!

About convert/017, well, the issue was odd really. BNut, good that it passes. Report again if this fails.

i'll try to take some time to investigate this more carefully. Thanks for report!

btw, would you like to edit the bug with the only remaining test failing?

ernsteiswuerfel commented 4 years ago

Just did a re-run of the full testsuite on top of 5.9-rc2 + patch. Strangely convert/017 failed again, run via ./convert-tests.sh but it passes when run as single test.

However I noticed 018-fs-size-overflow is failing now with convert/main.c:1161: do_convert: Assertion cctx.total_bytes failed, value 0 on the G4.

All the other tests pass or were correctly skipped. convert-tests-results.txt

marcosps commented 4 years ago

Just did a re-run of the full testsuite on top of 5.9-rc2 + patch. Strangely convert/017 failed again, run via ./convert-tests.sh but it passes when run as single test.

However I noticed 018-fs-size-overflow is failing now with convert/main.c:1161: do_convert: Assertion cctx.total_bytes failed, value 0 on the G4.

All the other tests pass or were correctly skipped. convert-tests-results.txt

Thanks for the report! I fixed the issue in my local branch: https://github.com/marcosps/btrfs-progs/tree/mpdesouza_convert_018

This fix was sent to ML, so I expect a review soon. I was able to create a x86 32bit VM, and so I managed to reproduce this issue and also convert/017 test.

I hope to have a fix for convert/017 soon too.

marcosps commented 4 years ago

@ernsteiswuerfel for convert/017 test I suspect that there is an issue in e2fsprogs w.r.t 32bit machines. I'm still investigating and already for help of some ext4 experts to see if this is the case. I should have an update soon.

marcosps commented 4 years ago

After analyzing better and having a response from an ext4 specialist, it does seem to be an issue in the e2fsprogs. The ext[234] code can change the allocation start/end in a non-deterministic way, so it does not seems to be related with the real issue. I'll keep checking.

adam900710 commented 4 years ago

By "non-deterministic", we still need to ensure that, e2fsprogs would never report a used space as free, right?

If e2fsprogs just reports more space than it really used, that won't cause any real problem except the failed tests, and we only need to update that convert/017 test case.

marcosps commented 3 years ago

By "non-deterministic", we still need to ensure that, e2fsprogs would never report a used space as free, right?

It seems not being the case as the used space is the same on a ext4 created on a i586 and x64 machine.

To update my current findings, as I didn't have time to check this again:

The test convert/017 creates a different allocation map when created on a x32 machine. In this particular case, there is some minor blocks being grouped, one block group using 10Mb, and another one with 50Kb IIRC.

Our convert code makes sure that a data chunk (the term used as a block group in btrfs) has at least 32Mb of size, so when it finds these two block groups it extents them to 32Mb. I still need to check whether this is strictly necessary or not.

This behavior makes btrfs reports more space being used (after all the calculations it shows 10Mb less of free space if we compare with the same ext4 image from an x64 machine), the btrfs-convert fails to find free space in the to be converted disk (test.img file in this case).

I hope to have more free time to work on it in the next few days.

marcosps commented 3 years ago

@ernsteiswuerfel can you confirm that issue 018-fs-size-overflow is fixed?

ernsteiswuerfel commented 3 years ago

@marcosps Yes, 018-fs-size-overflow passes now, thanks!

Tested on both ppc32/x86, Kernel 5.8.11, btrfs-devel + commit 8847cfe. All the other convert tests pass too, except 017-fs-near-full.

ernsteiswuerfel commented 3 years ago

Both cli-tests/014-multiple-profiles-warning and convert-tests/017-fs-near-full pass now on 32bit x86 (testet with btrfs-progs v5.10 on kernel 5.11-rc6).

marcosps commented 3 years ago

@ernsteiswuerfel good to know! I wonder what fixed them :) Anything, thanks a lot for testing!

ernsteiswuerfel commented 2 years ago

Hmm, seems I have to reopen this. Tested now on my Pentium4 box, btrfs-progs 5.16.1, kernel 5.17-rc3...

====== RUN CHECK mount -o loop -t ext4 /root/build/btrfs-progs/tests/test.img /root/build/btrfs-progs/tests/mnt
====== RUN CHECK dd if=/dev/zero bs=1M count=64 of=/root/build/btrfs-progs/tests/mnt/convert_space_holder status=noxfer
64+0 Datens?tze ein
64+0 Datens?tze aus
====== RUN CHECK fallocate -l 200M /root/build/btrfs-progs/tests/mnt/file1
====== RUN CHECK fallocate -l 200M /root/build/btrfs-progs/tests/mnt/file2
====== RUN CHECK fallocate -l 200M /root/build/btrfs-progs/tests/mnt/file3
====== RUN CHECK fallocate -l 200M /root/build/btrfs-progs/tests/mnt/file4
====== RUN CHECK fallocate -l 205M /root/build/btrfs-progs/tests/mnt/file1
====== RUN CHECK fallocate -l 205M /root/build/btrfs-progs/tests/mnt/file2
====== RUN CHECK fallocate -l 205M /root/build/btrfs-progs/tests/mnt/file3
====== RUN CHECK fallocate -l 205M /root/build/btrfs-progs/tests/mnt/file4
====== RUN CHECK umount /root/build/btrfs-progs/tests/test.img
====== RUN CHECK /root/build/btrfs-progs/btrfs-convert /root/build/btrfs-progs/tests/test.img
ERROR: failed to reserve 65536 bytes for temporary superblock, largest available: 0 bytes
ERROR: unable to create initial ctree: No space left on device
WARNING: error during conversion, the original filesystem is not modified
btrfs-convert from btrfs-progs v5.16.1

Source filesystem:
  Type:           ext2
  Label:          
  Blocksize:      4096
  UUID:           281f49b6-7592-41ed-ab80-a95dc4d461e9
Target filesystem:
  Label:          p�跴朿�朿p���tַ
locksize:      4096
  Nodesize:       16384
  UUID:           153f54f8-7a9f-4997-9801-c1e31a0210ea
  Checksum:       crc32c
  Features:       extref, skinny-metadata, no-holes (default)
    Data csum:    yes
    Inline data:  yes
    Copy xattr:   yes
Reported stats:
  Total space:      1073741824
  Free space:                0 (0.00%)
  Inode count:           65536
  Free inodes:           65520
  Block count:          262144
Create initial btrfs filesystem
failed: /root/build/btrfs-progs/btrfs-convert /root/build/btrfs-progs/tests/test.img
test failed for case 017-fs-near-full

convert-tests-results.txt.zip

ernsteiswuerfel commented 2 years ago

No change with btrfs-progs 5.18, kernel 5.18.0.

====== RUN CHECK /root/build/btrfs-progs/btrfs-convert /root/build/btrfs-progs/tests/test.img
ERROR: failed to reserve 33554432 bytes for metadata chunk, largest available: 29294592 bytes
ERROR: unable to create initial ctree: No space left on device
WARNING: error during conversion, the original filesystem is not modified
btrfs-convert from btrfs-progs v5.18

Source filesystem:
  Type:           ext2
  Label:          
  Blocksize:      4096
  UUID:           2e9b1051-f0d5-44dd-932b-37e8c0b50c9a
Target filesystem:
  Label:          
  Blocksize:      4096
  Nodesize:       16384
  UUID:           17012638-1c8c-4591-b27a-c3ac781b091b
  Checksum:       crc32c
  Features:       extref, skinny-metadata, no-holes (default)
    Data csum:    yes
    Inline data:  yes
    Copy xattr:   yes
Reported stats:
  Total space:      1073741824
  Free space:         37027840 (3.45%)
  Inode count:           65536
  Free inodes:           65520
  Block count:          262144
Create initial btrfs filesystem
failed: /root/build/btrfs-progs/btrfs-convert /root/build/btrfs-progs/tests/test.img
test failed for case 017-fs-near-full

convert-tests-results.txt.zip