Skip to content
  • Eric Sandeen's avatar
    ext4: don't print scary messages for allocation failures post-abort · e3570639
    Eric Sandeen authored
    
    
    I often get emails containing the "This should not happen!!" message,
    conveniently trimmed to remove things like:
    
    sd 0:0:0:0: [sda] Unhandled error code
    sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
    sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 03 13 c9 70 00 00 28 00
    end_request: I/O error, dev sda, sector 51628400
    Aborting journal on device dm-0-8.
    EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
    EXT4-fs (dm-0): Remounting filesystem read-only
    
    I don't think there is any value to the verbosity if the reason is
    due to a filesystem abort; it just obfuscates the root cause.
    
    Signed-off-by: default avatarEric Sandeen <sandeen@redhat.com>
    Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
    e3570639