linux-ext4 - [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-217965-13602-QKKfb6hXF9@https.bugzilla.kernel.org/>
Date:   Mon, 02 Oct 2023 15:55:08 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 217965] ext4(?) regression since 6.5.0 on sata hdd

https://bugzilla.kernel.org/show_bug.cgi?id=217965

--- Comment #4 from Ivan Ivanich (iivanich@...il.com) ---

(In reply to Theodore Tso from comment #3)
> What sort of information can you give about the ext4 file system where this
> is happening?  How much free space is there?   Can you run "df" and
> "dumpe2fs -h" on the system so we can see which file system features were
> enabled?   Also, can you specify the kind of the block device?
> 
> Differential debugging would be useful.  For example, can you try is to copy
> the file system image to a hardware, and see if you can reproduce the
> behavior using the same kernel build workload?   What if you copy to the
> file system image to a USB attached SSD, and see if you can reproduce the
> behavior?   What you attach the USB attached SSD, and use a freshly
> formatted ext4 file system?   Does it reproduce then?   If the file system
> is nearly full, what if you delete a lot of unused space, to provide a lot
> more free space, and see if it reproduces then?

mount |grep sdb2
/dev/sdb2 on /mnt/sdb2 type ext4 (rw,relatime,stripe=32752)

df /mnt/sdb2/
Filesystem      1K-blocks       Used Available Use% Mounted on
/dev/sdb2      2667140496 2125391752 539022500  80% /mnt/sdb2


dumpe2fs -h /dev/sdb2
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   <none>
Last mounted on:          /mnt/sdb2
Filesystem UUID:          3bd82ee7-f08a-4a23-8e50-2df3786b0858
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype
needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg
dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              169369600
Block count:              677467392
Reserved block count:     677465
Overhead clusters:        10682268
Free blocks:              135437186
Free inodes:              168057645
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      862
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              32752
Flex block group size:    16
Filesystem created:       Wed Jun 25 13:10:17 2014
Last mount time:          Mon Oct  2 18:46:12 2023
Last write time:          Mon Oct  2 18:46:12 2023
Mount count:              23
Maximum mount count:      -1
Last checked:             Thu Sep 28 14:37:21 2023
Check interval:           0 (<none>)
Lifetime writes:          84 TB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      a90aaa2d-577c-4181-83f9-696dee7ea92d
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Total journal size:       128M
Total journal blocks:     32768
Max transaction length:   32768
Fast commit length:       0
Journal sequence:         0x002a8661
Journal start:            9556

I don't have physical access to this machine so can't do any manipulations to
the hardware or attaching USB drives etc.

Device is 
Model Family:     Toshiba 3.5" DT01ACA... Desktop HDD
Device Model:     TOSHIBA DT01ACA300
Serial Number:    14KP58HGS
LU WWN Device Id: 5 000039 ff4d7b718
Firmware Version: MX6OABB0
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Oct  2 18:53:26 2023 EEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.