https://bugs.kde.org/show_bug.cgi?id=502290

            Bug ID: 502290
           Summary: Check and repair partition does not show error, and
                    does not try to repair
    Classification: Applications
           Product: partitionmanager
           Version: 24.12.0
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: andr...@stikonas.eu
          Reporter: feder...@kircheis.it
  Target Milestone: ---

I had a partition with an error, executing Check/Repair showed an error, the
detail windows showed:


----
Check and repair partition ‘/dev/sda1’ (1,00 TB, ext4)
Job: Check file system on partition ‘/dev/sda1’
Command: e2fsck -f -y -v /dev/sda1
Check file system on partition ‘/dev/sda1’: Error
Check and repair partition ‘/dev/sda1’ (1,00 TB, ext4): Error
----

When executing the same command from the command-line, I got

----
sudo e2fsck -f -y -v /dev/sda1
e2fsck 1.47.2 (1-Jan-2025)
The filesystem size (according to the superblock) is 244190385 blocks
The physical size of the device is 244190208 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? yes
----

STEPS TO REPRODUCE
1. Find a corrupt partition
2. Execute Repair/check
3. Verify that no details about the error are shown

OBSERVED RESULT
No details are shown, and there was no attempt to repair the partition

EXPECTED RESULT
The name "check/repair" implies that it would verify the partition and/or try
to repair it.
At least show the errors in case of error.


ADDITIONAL INFORMATION

After removing _y, I got the following output (after replying "n"), maybe using
-y is not a sensible choice when executing e2fsck (I do not now the tool good
enough to recommend something else)


----
sudo e2fsck -f -v /dev/sda1
e2fsck 1.47.2 (1-Jan-2025)
The filesystem size (according to the superblock) is 244190385 blocks
The physical size of the device is 244190208 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? n
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

      127273 inodes used (0.21%, out of 61054976)
       22153 non-contiguous files (17.4%)
         107 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 125755/1508
   210106788 blocks used (86.04%, out of 244190385)
           0 bad blocks
          18 large files

      122187 regular files
        5075 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           2 symbolic links (1 fast symbolic link)
           0 sockets
------------
      127264 files
----

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to