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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 07 Aug 2018 14:52:42 +0000
Subject: [Bug 200753] write I/O error for inode structure leads to operation
 failure without any warning or error

Martin Steigerwald ( changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #12 from Martin Steigerwald ( ---
Interesting. That may explain why on doing a "blkdiscard" on the partition of
an Ext4 filesystem mounted as / on an SSD does not seem to show anything in
"dmesg -w" started before the "blkdiscard" command. I always was quite a bit
puzzled about this. This happened with a running Plasma desktop which attempts
to write things quite regularly. When accessing a command not yet in cache I do
receive "error in format of binary file" (roughly translated from German
language). But still nothing in kernel log ring buffer. This is on some Fujitsu
workstation with Intel CPU + chipset. I assume the kernel uses libata AHCI for
accessing it. No access to such a workstation at the moment.

I made a test with creating an 1 exibyte large XFS filesystem on a large sparse
file on a way smaller XFS filesystem and on writing to the 1 exibyte large
filesystem beyond the free space left in the underlying XFS gave error messages
like "lost buffer write" in kernel log. I never tried the "blkdiscard" thing
with XFS so far tough.

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

Powered by blists - more mailing lists